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/storious/agent-playbook/agents-mdgit clone --depth 1 https://github.com/storious/agent-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/storious/agent-playbook/agents-md)<a href="https://agentmods.dev/instructions/storious/agent-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/storious/agent-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 | $0.00372 | $0.00372 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
agent-playbook 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 3d 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
Agent Playbook Maintainer
Session Bootstrap
- Read
.agents/agulater.jsonfor the top-level Agent Operational Contract. - Read
.agents/AGENTS.mdfor the portable operating contract. - Read
.agents/harness.jsonfor context, loop, tool, and checkpoint policy. - Read
.agents/context/core.mdbefore orienting to a new task. - Read
.agents/context/task-brief.mdand update the working set only for the active task. - Load a matching skill from
.agents/skills/only when its description fits the task.
Context Discipline
- Keep this root file short; it is a bootstrap route, not a full project dump.
- Treat the active working set and handoff as compact state, not hidden memory.
- When context pressure or a phase boundary occurs, preserve goal, evidence,
decisions, verification, risk, and the next action in
.agents/context/handoff.md.
Runtime Boundary
This configuration describes intended behavior. It does not grant tools, permissions, network access, file mutation, or background execution. The host runtime remains authoritative for those capabilities.
Project Rules
- Treat
.agents/agulater.jsonas this repository's dogfooded Agent Operational Contract. - Keep Agulater's owned model central: context, harness, loop, graph, capabilities, and evidence. External systems are references, not semantic authorities.
- When changing generated contract structure, update the generator, the root dogfood kit, the research example, tests, and audit together.
- Use Bun + TypeScript for authoring tools. Keep them local-only and do not add execution authority, model calls, or hidden memory.
- Validate with
bun run testbefore handing off a change.
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.
- 3d ago First seen · 37 lines · 372 tokens per session scan A 1d2cbcead40b
agent-playbook AGENTS.md is an instructions file published in the GitHub repository storious/agent-playbook (2 stars, last pushed 3d ago), licensed MIT. It adds 372 tokens to every session, about $0.0019 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
ocx AGENTS.md
Instructions for kdcokenny/ocx, a project described as: OpenCode extension manager with portable, isolated profiles. Your setup, anywhere.
fff AGENTS.md
AGENTS.md instructions for dmtrKovalenko/fff, covering to clankers, development commands, building, testing and development tools and code quality.
lola AGENTS.md
Instructions for LobsterTrap/lola, covering lola — agent instructions, working in this repo, development commands, python and go.
pi-coding-agent-forge AGENTS.md
Instructions for Firstp1ck/pi-coding-agent-forge, covering repository documentation rules, documentation goal, required documentation layers, readme.md — human guide and technical.md — advanced user reference.
agentconfig.org AGENTS.md
Instructions for agentconfig/agentconfig.org, covering agent instructions for agentconfig.org, project overview, target audience, site structure and tech stack.
rosetta AGENTS.md
Instructions for tikoci/rosetta, covering codex instructions for rosetta, first reads, development defaults and mcp and client config.