Report · marked 25 Aug 2026
code-yeongyu/oh-my-openagent
Solid foundations, held back in a few specific places.
TypeScript · 68,363 stars · 9,127 files · branch dev
81
/100
A-
Instructions
25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
18/20Whether an agent can install the project and get it running without a human. Losing marks on pinned runtime version.Verification loop
22/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.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
7/10How quickly anything new can orient itself. Losing marks on license.
Higher is better. Accent marks what is costing you most.
Fix these first
01
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.
02
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.
03
Repository weight
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
The full marking
Every deduction below names the file or setting it came from.
Instructions 25/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.
Also found: CLAUDE.md
✗Instruction quality
10/12
Specific enough that an agent can act on it.
Worth fixing: it's 62k characters, which burns context on every single turn.
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 18/20 A
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
bun.lock pins the dependency tree.
Found bun.lock
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (build, build:cli-node, build:codex-install, install:codex-dev, build:codex-plugin, build:senpi-plugin…)
✓Environment config
4/4
.env.example documents what the app needs to 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
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 22/25 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
2509 test files against 6279 source files.
e.g. .agents/skills/codex-qa/scripts/lib/app-server-client.test.js, .agents/skills/senpi-qa/scripts/resolve-evidence-dir.test.mjs, .omo/evidence/20260719-fix-6131-stale-guard/root-bun-test.txt
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
11 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
3/3
Strict type checking is on, which catches a whole class of agent mistakes before they run.
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 46 patterns.
✗File sizes fit in context
0/6
11 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.
packages/omo-senpi/plugin/extensions/omo.js — 851KB
packages/omo-senpi/plugin/extensions/omo-task.js — 589KB
packages/omo-codex/scripts/install-dist/install-local.mjs — 484KB
✗Repository weight
2/5
About 160MB 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 omo/lazycodex: The coding agent for tokenmaxxers;the one and only agent harness for complex codebases. For your Codex, for your OpenCode ## Setup ``` bun install ``` ## Commands ``` bun build # produce a build bun test # run the test suite, must pass before any commit bun typecheck # type check without emitting bun build:cli-node bun build:codex-install bun install:codex-dev bun build:codex-plugin bun build:senpi-plugin ``` ## Layout - `packages/` 6037 source files - `script/` 105 source files - `tests/` 11 source files - `bin/` 7 source files - `scripts/` 3 source files - `test-support/` 1 source file ## Conventions - Tests live alongside the code they cover, following `.agents/skills/codex-qa/scripts/lib/app-server-client.test.js`. - TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it. - 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 - `packages/omo-senpi/plugin/extensions/omo.js` is 851KB. 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/code-yeongyu/oh-my-openagent.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/code-yeongyu/oh-my-openagent)Other TypeScript 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.