agentreadme

Report · marked 25 Aug 2026

Fission-AI/OpenSpec

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

TypeScript · 66,217 stars · 1,132 files · branch main

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.

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.
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 16/16 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 (lint, build, generate:skills, regen:parity-hashes, dev, dev:cli…)
scripts/ directory
Environment config n/a
Not applicable — this reads as a library, with no environment to configure.
Pinned runtime version 2/2
The language runtime version is pinned.
package.json engines.node >=20.19.0
Reproducible environment 2/2
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 25/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
363 test files against 371 source files.
e.g. openspec/changes/add-change-stacking-awareness/specs/change-creation/spec.md, openspec/changes/add-change-stacking-awareness/specs/change-stacking-workflow/spec.md, openspec/changes/add-change-stacking-awareness/specs/cli-change/spec.md
Test command is discoverable 7/7
An agent can find and run `npm run test`.
Continuous integration 4/4
3 GitHub Actions workflows define what "passing" means.
Lint and format rules 3/3
eslint.config.js encodes the house style.
Static type checking 3/3
Strict type checking is on, which catches a whole class of agent mistakes before they run.
Context economy 18/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 73 patterns.
File sizes fit in context 4/6
2 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.
test/core/archive.test.ts — 299KB
test/core/update.test.ts — 145KB
Repository weight 5/5
About 7.6MB 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 Fission-AI/OpenSpec
undefined

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/Fission-AI/OpenSpec.md

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 86 out of 100

[![agent ready](https://agentreadme.com/badge/Fission-AI/OpenSpec.svg)](https://agentreadme.com/Fission-AI/OpenSpec)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 68 B nilbuild/developer-roadmap 45 C vuejs/vue 67 B n8n-io/n8n 87 A anomalyco/opencode 80 A-

All TypeScript 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