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/neeeophytee/agent-stylebooks/agents-mdgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/agents-md)<a href="https://agentmods.dev/instructions/neeeophytee/agent-stylebooks/agents-md"><img src="https://agentmods.dev/badge/instructions/neeeophytee/agent-stylebooks/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.00132 | $0.00132 |
| Opus 5 | $0.00066 | $0.00066 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
agent-stylebooks 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 5d 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
Repository instructions
- Preserve the original 11 skills byte-for-byte unless an objective compatibility bug is reported.
- Run
python3 scripts/validate_repo.pyafter modifying skills, manifests, catalog docs, provenance, or validation code. - Do not copy source-guide passages or examples into this repository.
- Do not upgrade a reference-only source to open-license status without an authoritative license URL.
- Keep facts, legal meaning, commands, and code unchanged when testing a style.
- Do not push, publish, create a release, or create a remote unless the user asks.
- Keep model eval infrastructure out of v0.2.
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.
- 5d ago First seen · 12 lines · 132 tokens per session scan A 127771ecc6cd
agent-stylebooks AGENTS.md is an instructions file published in the GitHub repository Neeeophytee/agent-stylebooks (58 stars, last pushed 12d ago), licensed MIT. It adds 132 tokens to every session, about $0.0007 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
write-me-a-readme AGENTS.md
AGENTS.md instructions for thuanvd378/write-me-a-readme, covering repository guidance, source of truth, content rules, implementation rules and verification.
velocity CLAUDE.md
Claude Code instructions for OptimiLabs/velocity, covering velocity — project guidelines, tech stack, key architecture, conventions and tables.
core copilot-instructions.md
Copilot instructions for asdecided/core: These decisions are already accepted. Do not re-open or contradict them; ask the AsDecided MCP tools (getartifact, searchartifacts) for the full text before proposing a change that touches one.
docs AGENTS.md
Instructions for argos-ci/docs, covering agents.md, always use the documentation skills and keep the table of contents in sync.
everything-gemini-code GEMINI.md
Gemini CLI instructions for Jamkris/everything-gemini-code, covering project instructions, prompt defense baseline and guidelines.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.