Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/agent-next/agent-ready/claude-mdgit clone --depth 1 https://github.com/agent-next/agent-readyWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00519 | $0.00519 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
agent-ready CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-ready
Best practices collection for high-quality GitHub repos + AI coding agent workflows. TypeScript, Node 20+, Commander CLI.
Commands
npm install # install dependencies
npm run dev -- check . # run CLI in dev mode
npm test # 102 tests, node test runner
npm run test:coverage # coverage with c8
npm run typecheck # tsc --noEmit
npm run lint # eslint
npm run format # prettier
npm run check # typecheck + lint + format (all gates)
npm run build # tsc → dist/
Architecture
src/index.ts (CLI entry, commander)
→ src/commands/check.ts → src/checker.ts (9-area readiness checker)
→ src/commands/init.ts (file generation)
src/checker.ts
→ src/engine/context.ts (build scan context, detect language + project type)
→ src/utils/fs.ts (fileExists, readFile, findFiles)
packages/mcp/ (MCP server, check_repo_readiness tool)
skill/agent-ready/ (SKILL.md + 8 reference docs + BDT testing refs)
Conventions
- TypeScript strict mode, interfaces over types, avoid
any - Files:
kebab-case.ts, interfaces:PascalCase, functions:camelCase - Area names:
agent_guidance,code_quality,testing,ci_cd,hooks,branch_rulesets,templates,devcontainer,security - Export all types from
src/types.ts - Keep checks pure — no external API calls, scanning is local only
Testing
- Runner:
tsx --test(Node built-in test runner) - Test files mirror source:
src/checker.ts→test/checker.test.ts - Fixtures in
test/fixtures/(minimal-repo, standard-repo, l3-repo, monorepo, python-repo, empty-repo) - Run tests after every change:
npm test - Update tests in the same pass as code changes
Git
- Atomic commits, one logical change per commit
- Branch naming:
feat/,fix/,docs/,chore/ - PR titles: semantic prefix (
feat:,fix:,docs:, etc.) - Run
npm run checkbefore committing
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 59 lines · 519 tokens per session scan A 1d37fb4d3fae
agent-ready CLAUDE.md is an instructions file published in the GitHub repository agent-next/agent-ready (27 stars, last pushed 3mo ago), licensed MIT. It adds 519 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
deer-flow CLAUDE.md
Claude Code instructions for bytedance/deer-flow: The repo's agent guidance lives in AGENTS.md so it is shared across coding agents (Claude Code, Codex, and others). Claude Code imports it below.
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
sprawling AGENTS.md
Instructions for 2youg1/sprawling, covering agents.md — how work is done in this repository, the loop, read before you write, one change, five steps and the rules a machine holds.
open-vibe-island CLAUDE.md
Claude Code instructions for Octane0411/open-vibe-island, covering claude.md, project, architecture, build & run and dev app (open island dev.app).
codehydra CLAUDE.md
Instructions for stefanhoelzl/codehydra, covering claude.md, critical rules, no ignore comments, api/ipc interface changes and new boundary interfaces.
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.