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 skills add rennf93/opus-fable-playbook --skill fable-fanoutgit 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/skills/rennf93/opus-fable-playbook/fable-fanout)<a href="https://agentmods.dev/skills/rennf93/opus-fable-playbook/fable-fanout"><img src="https://agentmods.dev/badge/skills/rennf93/opus-fable-playbook/fable-fanout/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/skills/rennf93/opus-fable-playbook/fable-fanout"><img src="https://agentmods.dev/badge/skills/rennf93/opus-fable-playbook/fable-fanout.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.00043 | $0.00382 |
| Opus 5 | $0.00022 | $0.00191 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
fable-fanout 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.
What it actually says
Fable Fanout
Fable never works serially on independent work. Decision tree:
- Single fact, known location (one file, one symbol, one value) → direct tool call. Delegation would be overhead.
- Broad or multi-file question ("where is X handled", "how does Y
flow") → delegate to the
Exploreagent (read-only, returns conclusions). IfExploreis unavailable, usegeneral-purpose. - 2+ independent units of work → spawn one agent per unit, ALL IN ONE MESSAGE (parallel tool-use block). Never spawn one, wait, spawn the next.
- Agents that mutate files in parallel → give each
isolation: "worktree"or disjoint file sets; never two writers on one file. - After the fan-out → you own synthesis. Read the agents' conclusions, resolve conflicts, and write the unified final answer yourself. Never paste agent output as the deliverable.
Required subagent prompt template
Subagents do not see the Fable output style — propagate doctrine in every spawn prompt. Append this to every agent prompt, verbatim:
Return conclusions, not file dumps. Report failures verbatim. Your final message is your return value — raw findings for the caller, not a human-facing message. Include file:line references for every claim.
While agents run
Don't idle-poll and don't redo their work yourself. If you delegated a search, trust the result; verify only what's load-bearing.
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 · 36 lines · 43 tokens per session scan A fde167c61a91
fable-fanout is a skill published in the GitHub repository rennf93/opus-fable-playbook (34 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 382 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 skills, from other repositories
confidence-gate
When you're about to claim success ("fixed", "done", "works", "passing tests") at the end of a turn, verify the claim is backed by actual evidence in this session. presence's Stop hook will flag a success claim that has no recent test/build pass behind it. Be aware of this gate and either run the verification, or…
are-you-done
A completion checker for coding work that asks for evidence before allowing an assistant to say a task is finished.
did-you-forget-me
A requirement-checking skill that compares the current work with what the user explicitly asked for. It is written in Korean and includes a fixed Korean report format.
dont-leave-me
A stop-before-finishing checklist for an agent that checks whether requested work, changed files, verification, and cleanup have actually been handled.
show-me-proof
A skill for collecting concrete proof that a coding task was completed, such as changed files, test commands, logs, and remaining risks.
baton-setup
One-time setup and health check for fable-baton. Use when the user asks to set up, configure, verify, or troubleshoot fable-baton - sets the default model to "best" (Fable 5 with Opus fallback) in /.claude/settings.json and verifies the plugin is fully installed.