Report · marked 27 Aug 2026
tinyhumansai/openhuman
Solid foundations, held back in a few specific places.
Rust · 38,223 stars · 5,148 files · branch main
75
/100
B+
Instructions
15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
20/20Whether an agent can install the project and get it running without a human. Full marks.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
11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
9/10How quickly anything new can orient itself. Losing marks on repository description.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Instruction quality
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
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 15/27 B-
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.
Also found: CLAUDE.md
✗Instruction quality
0/12
The file exists but couldn't be read for scoring.
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 20/20 A+
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (build, docs:generate, docs:check, docs:test, test:scripts, test:inventory…)
scripts/ directory
✓Environment config
4/4
.env.example documents what the app needs to run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
Found rust-toolchain.toml
✓Reproducible environment
2/2
dockerfile gives a known-good environment.
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
1184 test files against 4335 source files.
e.g. app/scripts/e2e-run-spec.sh, app/src/AppRoutes.auth.test.tsx, app/src/AppRoutesIOS.test.tsx
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
19 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 11/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 92 patterns.
✗File sizes fit in context
0/6
38 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.
app/src/lib/i18n/bn.ts — 667KB
app/src/lib/i18n/hi.ts — 648KB
app/src/lib/i18n/ru.ts — 565KB
✗Repository weight
2/5
About 177MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
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 Your Personal AI super intelligence. A brain that builds a local-first memory of your life, a fantastic orchestrator of agent fleets and workflows, and a deep researcher. ## Setup ``` pnpm install ``` ## Commands ``` pnpm dev # run locally pnpm build # produce a build pnpm test # run the test suite, must pass before any commit pnpm typecheck # type check without emitting pnpm lint # lint pnpm format # format pnpm docs:generate pnpm docs:check ``` ## Layout - `app/` 2082 source files - `src/` 1866 source files - `scripts/` 220 source files - `tests/` 130 source files - `packages/` 18 source files - `e2e/` 8 source files ## Conventions - Tests live alongside the code they cover, following `app/scripts/e2e-run-spec.sh`. - CI defines what passing means. See `.github/workflows/android-compile.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `app/src/lib/i18n/bn.ts` is 667KB. It will not fit comfortably in context, so read it in parts. - Copy `.env.example` before running anything that needs configuration. --- 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/tinyhumansai/openhuman.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/tinyhumansai/openhuman)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.