Report · marked 25 Aug 2026
AlexsJones/llmfit
Solid foundations, held back in a few specific places.
Rust · 34,033 stars · 243 files · branch main
84
/100
A-
Instructions
27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup
14/20Whether an agent can install the project and get it running without a human. Losing marks on environment config and pinned runtime version.Verification loop
19/25Whether 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 and static type checking.Context economy
16/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
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.
02
File sizes fit in context
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.
03
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
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.
12,869 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 14/20 B+
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
6/6
Commands are declared where an agent will look for them.
Makefile
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
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
✓Reproducible environment
2/2
dockerfile gives a known-good environment.
Verification loop 19/25 B+
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
14 test files against 72 source files.
e.g. llmfit-core/tests/fixtures/hardware/mixed/rocm-product.txt, llmfit-core/tests/fixtures/hardware/mixed/rocm-vram.txt, llmfit-core/tests/fixtures/hardware/mixed/vulkan-malformed.txt
✓Test command is discoverable
7/7
An agent can find and run `make test`.
✓Continuous integration
4/4
7 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
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 16/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 15 patterns.
✗File sizes fit in context
2/6
8 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.
llmfit-core/src/providers.rs — 224KB
llmfit-tui/src/tui_app.rs — 211KB
llmfit-tui/src/tui_ui.rs — 207KB
✓Repository weight
5/5
About 27.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 Hundreds of models & providers. One command to find what runs on your hardware. ## Setup ``` cargo build ``` ## Commands ``` make help make build # produce a build make release make clean make run make test # run the test suite, must pass before any commit ``` ## Layout - `llmfit-web/` 22 source files - `llmfit-core/` 18 source files - `llmfit-tui/` 14 source files - `scripts/` 9 source files - `llmfit-desktop/` 4 source files - `llmfit-python/` 4 source files ## Conventions - Tests live alongside the code they cover, following `llmfit-core/tests/fixtures/hardware/mixed/rocm-product.txt`. - CI defines what passing means. See `.github/workflows/ci.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `llmfit-core/src/providers.rs` is 224KB. 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/AlexsJones/llmfit.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/AlexsJones/llmfit)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.