Report · marked 10 Oct 2026

TheAlgorithms/Python

Ready for an agent to work in without hand-holding.

Python · 225,144 stars · 1,733 files · branch master

89 /100 A

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 16/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop 18/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and static type checking.Context economy 20/20Whether the repo fits in a context window, or fights it. Full marks.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

Environment config

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

Tests exist

Coverage is thin enough that an agent can break real behavior and still see green.

Static type checking

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

The full marking

Every deduction below names the file or setting it came from.

Instructions 27/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

✓Instruction quality 12/12

Specific enough that an agent can act on it.

2,891 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 16/20 A-

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

uv.lock pins the dependency tree.

Found uv.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 0/4

Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

Found .python-version

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

Verification loop 18/25 B+

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✗Tests exist 4/8

38 test files against 1611 source files.

Coverage is thin enough that an agent can break real behavior and still see green.

e.g. data_structures/hashing/tests/__init__.py, data_structures/hashing/tests/test_hash_map.py, data_structures/kd_tree/tests/__init__.py

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✓Continuous integration 4/4

8 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

pyproject.toml encodes the house style.

✗Static type checking 0/3

No static type checking.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

Context economy 20/20 A+

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 65 patterns.

✓File sizes fit in context 6/6

No source file is large enough to crowd out a context window.

✓Repository weight 5/5

About 18.3MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for TheAlgorithms/Python

# AGENTS.md

All Algorithms implemented in Python

## Setup

```
uv sync
```

## Commands

```
pytest         # run the test suite
ruff check .   # lint
```

## Layout

- `project_euler/`   322 source files
- `maths/`           219 source files
- `data_structures/` 150 source files
- `graphs/`          73 source files
- `strings/`         67 source files
- `sorts/`           60 source files

## Conventions

- Tests live alongside the code they cover, following `data_structures/hashing/tests/__init__.py`.
- CI defines what passing means. See `.github/workflows/build.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/TheAlgorithms/Python.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Python AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/TheAlgorithms/Python.svg)](https://agentreadme.com/TheAlgorithms/Python)

Other Python repositories, marked

vinta/awesome-python 81 A- NousResearch/hermes-agent 84 A- yt-dlp/yt-dlp 54 C+ microsoft/markitdown 48 C+ Significant-Gravitas/AutoGPT 65 B anthropics/skills 30 D

All Python repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in