Report · marked 25 Aug 2026
sharkdp/bat
An agent can work here, but it will waste turns finding its footing.
Rust · 60,257 stars · 913 files · branch master
56
/100
B-
Instructions
3/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
8/18Whether an agent can install the project and get it running without a human. Losing marks on discoverable commands and environment config.Verification loop
19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy
14/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context.Navigability
10/10How quickly anything new can orient itself. Full marks.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Agent instruction file
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
02
Instruction quality
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
03
Discoverable commands
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
The full marking
Every deduction below names the file or setting it came from.
Instructions 3/27 F
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
0/12
None found. Every agent that opens this repo starts from zero.
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
Looked for AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursorrules
✗Instruction quality
0/12
Nothing to judge, since there are no instructions.
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 8/18 C
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
cargo.lock pins the dependency tree.
Found cargo.lock
✗Discoverable commands
0/6
No declared commands. An agent has to infer how to build and run this from the file tree.
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
✗Environment config
2/4
Env vars are mentioned in the README but there's no example file to copy.
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
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 19/22 A
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
680 test files against 168 source files.
e.g. tests/.gitattributes, tests/assets.rs, tests/benchmarks/.gitignore
✓Test command is discoverable
7/7
An agent can find and run `cargo test`.
✓Continuous integration
4/4
2 GitHub Actions workflows define what "passing" means.
✗Lint and format rules
0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
–Static type checking
n/a
Not applicable — the Rust compiler type checks every build.
Context economy 14/20 B+
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 11 patterns.
✗File sizes fit in context
0/6
3 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
tests/benchmarks/highlighting-speed-src/numpy_test_multiarray.py — 310KB
tests/benchmarks/highlighting-speed-src/jquery.js — 265KB
tests/integration_tests.rs — 143KB
✓Repository weight
5/5
About 35.2MB 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 A cat(1) clone with wings. ## Setup ``` cargo build ``` ## Commands ``` cargo test # run the test suite ``` ## Layout - `tests/` 114 source files - `src/` 40 source files - `examples/` 7 source files - `build/` 4 source files - `assets/` 2 source files - `diagnostics/` 1 source file ## Conventions - Tests live alongside the code they cover, following `tests/.gitattributes`. - CI defines what passing means. See `.github/workflows/CICD.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - Generated output is committed (`build/`). Search will return the compiled copy, so edit the source, not that. - `tests/benchmarks/highlighting-speed-src/numpy_test_multiarray.py` is 310KB. It will not fit comfortably in context, so read it in parts. --- 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/sharkdp/bat.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/sharkdp/bat)Other Rust repositories, marked
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.