Borrowing it
Nothing to install: this file belongs to agent-next/agent-ready. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agent-next/agent-ready/main/CLAUDE.mdgit clone --depth 1 https://github.com/agent-next/agent-readyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/agent-next/agent-ready/claude-md)<a href="https://agentmods.dev/instructions/agent-next/agent-ready/claude-md"><img src="https://agentmods.dev/badge/instructions/agent-next/agent-ready/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/agent-next/agent-ready/claude-md"><img src="https://agentmods.dev/badge/instructions/agent-next/agent-ready/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00519 | $0.00519 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (35 stars, last pushed yesterday), licensed MIT. It adds 519 tokens to every session, about $0.0021 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.