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/rennf93/opus-fable-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/commands/rennf93/opus-fable-playbook/fable-eval)<a href="https://agentmods.dev/commands/rennf93/opus-fable-playbook/fable-eval"><img src="https://agentmods.dev/badge/commands/rennf93/opus-fable-playbook/fable-eval.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.00038 | $0.00264 |
| Opus 5 | $0.00019 | $0.00132 |
| Sonnet 5 | $0.00008 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
fable-eval 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 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.
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
Run the fable-mode convergence evals. $ARGUMENTS may contain a probe id
filter (e.g. 03), and --yes to skip the cost confirmation.
- Unless
--yeswas passed, tell the user how many probe runs this is (matched probes × 2 candidate modes + judging) and ask to proceed. - Ensure goldens exist in
evals/golden/for the matched probes; for any missing, generate:evals/run-probe.sh <probe> golden evals/golden. - Run baseline + fable candidates into
evals/results/<today>/, then judge each against its golden, per evals/LOOP.md steps 1–2 (respect the filter). - Run
evals/report.sh evals/results/<today>/and present the table. - Interpret per LOOP.md step 4: name the weakest dimension and the exact doctrine section/hook/skill to strengthen. Do not apply changes — recommend them.
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 · 19 lines · 0 tokens per session scan A eda8db6e79d1
fable-eval is a command published in the GitHub repository rennf93/opus-fable-playbook (34 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 264 once invoked, about $0.0002 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 commands, from other repositories
autoresearch
Autonomous improvement loop — scan codebase metrics, scaffold experiment files, run agent-driven iterations until metric improves.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
plan-validate
2-layer plan validation: instant structural checks + trigger-based specialist agents. Auto-fixes issues using ADRs and first principles. Every issue must be resolved before execution.
symfony-fixtures
Create test fixtures using Foundry factories for realistic test data.
symfony-tdd-pest
Start a TDD workflow using Pest PHP for Symfony with RED-GREEN-REFACTOR cycle.