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/ameenmari/agentprodready/agents-mdgit clone --depth 1 https://github.com/ameenmari/agentprodreadyWrote 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/ameenmari/agentprodready/agents-md)<a href="https://agentmods.dev/instructions/ameenmari/agentprodready/agents-md"><img src="https://agentmods.dev/badge/instructions/ameenmari/agentprodready/agents-md.svg" alt="Measured on agentmods" 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 | $0.00272 | $0.00272 |
| Opus 5 | $0.00136 | $0.00136 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
agentprodready AGENTS.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 4d 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.
What it actually says
AgentProdReady Agent Instructions
Before changing code or implementation documentation, read docs/cursor-start-here.md.
- Follow the architectural authority order defined in the documentation.
- Implement exactly one blueprint at a time.
- Declare one Implementation Mode from docs/implementation/implementation-modes.md.
- Create the canonical implementation plan and Blueprint Implementation Specification before production code.
- Use only plans, specifications, reports, checklists, and reviews for implementation artifacts.
- Use docs/architecture/dependency-graph.md as the authoritative dependency source.
- Respect accepted ADRs, explicit ownership, Runtime control, Security authorization ownership, Composition instantiation ownership, and provider boundaries.
- Apply the documented bootstrapping rules without transferring ownership or inventing final guarantees.
- Stop only for a documented stop condition; record reasonable implementation-level decisions in the specification.
- Never claim completion without successful required tests, an implementation report, and the completed blueprint-specific checklist.
- Never silently redesign architecture or implement more than the active blueprint authorizes.
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.
- 4d ago First seen · 16 lines · 272 tokens per session scan A 5a33b66dec33
agentprodready AGENTS.md is an instructions file published in the GitHub repository ameenmari/agentprodready (5 stars, last pushed 22d ago), licensed MIT. It adds 272 tokens to every session, about $0.0014 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-31.
Other instructions, from other repositories
pydantic-ai AGENTS.md
AGENTS.md instructions for pydantic/pydantic-ai, covering your primary responsibility is to the project and its users, gathering context on the task, ensuring the task is ready for implementation, philosophy and requirements of all contributions.
claude-tap AGENTS.md
Instructions for liaohch3/claude-tap, covering maintainer automation notes, agents 索引, documentation boundary, review guidelines and pre-commit hook.
waku-agent CLAUDE.md
Instructions for ShenSeanChen/waku-agent, covering waku-agent — working conventions, architecture map (file ↔ diagram box), rules and commands.
goai AGENTS.md
AGENTS.md instructions for zendev-sh/goai, covering agents.md - goai, commands, architecture, key rules and adding providers.
gitlab-mcp-server mcp-best-practices.instructions.md
MCP protocol-level best practices for tool design, annotations, response formats, pagination, and security. Applies to all Go MCP server code.
sagemath-mcp CLAUDE.md
Instructions for XBP-Europe/sagemath-mcp, covering claude.md, project, commands, linting and testing.