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/duolahypercho/fusion-fableWrote 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/duolahypercho/fusion-fable/fusion-opus4.8)<a href="https://agentmods.dev/commands/duolahypercho/fusion-fable/fusion-opus4.8"><img src="https://agentmods.dev/badge/commands/duolahypercho/fusion-fable/fusion-opus4.8/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/commands/duolahypercho/fusion-fable/fusion-opus4.8"><img src="https://agentmods.dev/badge/commands/duolahypercho/fusion-fable/fusion-opus4.8.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.00031 | $0.00233 |
| Opus 5 | $0.00015 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
fusion-opus4.8 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 12d 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
Invoke the fusion skill on the task below, forcing the opus4.8-4.8 panel:
run the same prompt twice as TWO independent Opus 4.8 panelists (Agent subagents, in parallel, neither
seeing the other's work) → Opus 4.8 judges both answers → Opus writes the final answer grounded in the
analysis.
Follow the skill's SKILL.md exactly (fan out in parallel → judge → grounded final answer) and present the standard sections (Consensus / Contradictions / Partial coverage / Unique insights / Blind spots / Final answer). Do NOT add a GPT-5.5 or Gemini panelist, even if codex/gemini are installed — this command is pinned to the pure-Opus panel. Do not assign the two runs any "lenses" — pass the task verbatim to both.
Task: $ARGUMENTS
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.
- 12d ago First seen · 16 lines · 31 tokens per session scan A 73c78d222659
fusion-opus4.8 is a command published in the GitHub repository duolahypercho/fusion-fable (472 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 233 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.