Borrowing it
Nothing to install: this file belongs to Wizarck/ai-playbook. 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/Wizarck/ai-playbook/main/AGENTS.mdgit clone --depth 1 https://github.com/Wizarck/ai-playbookWrote 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/wizarck/ai-playbook/agents-md)<a href="https://agentmods.dev/instructions/wizarck/ai-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/wizarck/ai-playbook/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.1 | $0.04204 | $0.04204 |
| Opus 5 | $0.02102 | $0.02102 |
| Sonnet 5 | $0.00841 | $0.00841 |
| Haiku 4.5 | $0.00420 | $0.00420 |
Grade C, and why
ai-playbook AGENTS.md scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Irreversible action confirmations** — `rm -rf`, `git push --force`, drop database, force-merge, etc. How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-playbook — self-hosted dispatcher
Read by agents working ON this repo (not consumers). Consumers read own project's AGENTS.md, inheriting from playbook via .ai-playbook/specs/*.
0 Bootstrap directive
Agents editing this repo MUST:
- Read
docs/concepts/dispatcher-chain.md— inheritance + override semantics. - Read
specs/agents-md-v1.schema.json— frontmatter contract before editingAGENTS.md. - Read
docs/rules/verdict-contract.rule.md— verdict + severity rubric before QA. - Then act.
1 Project identity
ai-playbook = universal norms + tooling repo. Submoduled by every consumer project. LLM-agnostic. Dogfoods own pre-commit + schema.
2 Dispatcher index
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.
- 7d ago First seen · 262 lines · 4,204 tokens per session scan C af1f4fea9948
ai-playbook AGENTS.md is an instructions file published in the GitHub repository Wizarck/ai-playbook (6 stars, last pushed 10d ago), licensed MIT. It adds 4,204 tokens to every session, about $0.0210 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.