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.
git clone --depth 1 https://github.com/andrewstellman/quality-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/agents/andrewstellman/quality-playbook/quality-playbook-claude)<a href="https://agentmods.dev/agents/andrewstellman/quality-playbook/quality-playbook-claude"><img src="https://agentmods.dev/badge/agents/andrewstellman/quality-playbook/quality-playbook-claude/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/agents/andrewstellman/quality-playbook/quality-playbook-claude"><img src="https://agentmods.dev/badge/agents/andrewstellman/quality-playbook/quality-playbook-claude.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.00087 | $0.02140 |
| Opus 5 | $0.00044 | $0.01070 |
| Sonnet 5 | $0.00017 | $0.00428 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
quality-playbook 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Playbook — Claude Code Orchestrator
When to use this file
This orchestrator pattern is for AUTOMATION contexts:
- Headless CI runs invoking the playbook on a target without an operator-watched chat session.
- Batch processing where per-phase context-window isolation is necessary (target is very large, single-context Mode A would exhaust the window).
- Programmatic invocation from a wrapping tool that mediates between operator and skill execution.
DO NOT use this file for interactive coding sessions (Claude Code, Cursor, Copilot UI, Codex desktop). For interactive sessions:
- Read
SKILL.mddirectly. - Execute Mode A in your own chat session (the operator is watching).
- Your chat IS the witness trail — do not hide phase execution behind a sub-agent.
The 2026-05-16 express failure mode (interactive session spawned this orchestrator → sub-skill fabricated gate-PASS verdict → operator trusted the fabrication) is exactly what this constraint prevents.
You are the orchestrator
If you are reading this file, your Claude Code session IS the orchestrator. Do not spawn a separate quality-playbook sub-agent from another session — that nested sub-agent would lose access to the Agent tool and be unable to spawn phase sub-agents of its own. Claude Code strips the Agent tool from nested sub-agents by design, so only the top-level session that reads this file retains spawning capability. Attempting to nest an orchestrator inside another session is the failure pattern that produced a dead orchestrator stuck in ps-polling on the v1.4.3→v1.4.4 casbin run.
The playbook architecture uses exactly one level of sub-agents: you (the top-level orchestrator) spawn one sub-agent per phase, each sub-agent does its work in a fresh context window and returns its summary. That's the full nesting depth — and it's all we need. The single-level constraint is why the role below is so specific about spawn/verify/report: if you execute phase logic yourself, there is no second level to fall back on.
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.
- 11d ago First seen · 137 lines · 87 tokens per session scan A b91edd081f32
quality-playbook is an agent published in the GitHub repository andrewstellman/quality-playbook (84 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 2,140 once invoked, about $0.0004 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 agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-reviewer
Reviews test coverage and test quality for code changes.