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 duolahypercho/fusion-fable --skill fusion-plangit 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/skills/duolahypercho/fusion-fable/fusion-plan)<a href="https://agentmods.dev/skills/duolahypercho/fusion-fable/fusion-plan"><img src="https://agentmods.dev/badge/skills/duolahypercho/fusion-fable/fusion-plan/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/duolahypercho/fusion-fable/fusion-plan"><img src="https://agentmods.dev/badge/skills/duolahypercho/fusion-fable/fusion-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 82 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 83 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Rogue Agent · line 119 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00266 | $0.03010 |
| Opus 5 | $0.00133 | $0.01505 |
| Sonnet 5 | $0.00053 | $0.00602 |
| Haiku 4.5 | $0.00027 | $0.00301 |
Grade A, and why
fusion-plan 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion-Plan — OMC interview, then a 3-round iterative panel
This skill follows the OMC plan system: requirements are gathered by OMC's real interview FIRST, then the fusion panel deepens the resulting plan, and the output flows back into OMC's review → execution pipeline. The fusion panel replaces only the plan-thinking step; storage, format, the quality gate, and execution all stay on OMC's rails.
Hard rule (same as fusion): Opus 4.8 always judges and synthesizes. You are the judge — stay separate from the panelists. The Opus panelist is always a spawned subagent, never you.
Step 0 — Requirements (pick the mode FIRST)
Decide interactive vs non-interactive before doing anything — this determines whether you may interview.
- Non-interactive when ANY of these is true: invoked with
--no-interview; running autonomously while executing a larger plan; running inside a spawned sub-agent; or you otherwise cannot reach a human who will answer. This is the default during plan execution. - Interactive only when a human is clearly present and able to answer right now — typically the user
typed
/fusion-plan ...directly in the main session at the start of a planning session.
Non-interactive mode (autonomous / sub-agent / --no-interview)
HARD RULE: do NOT interview. Do NOT call AskUserQuestion. Do NOT auto-chain the omc-plan interview.
There is no one to answer — blocking on a question would hang the run. Requirements were already gathered
upstream, so derive SEED_PLAN from the context that already exists, in this order:
- The task/story doc if one exists (e.g.
docs/stories/STORY-<id>.md). - The larger plan that flagged this task (e.g. the relevant
.omc/plans/*.mdsection). - The task description / prompt args you were given.
If that context is genuinely insufficient to plan, do NOT guess and do NOT ask — stop and return a short note listing exactly what's missing, so the human (or the orchestrator) resolves it. Then go to Step 1.
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 · 197 lines · 266 tokens per session scan A 39b5381d72b4
fusion-plan is a skill published in the GitHub repository duolahypercho/fusion-fable (471 stars, last pushed 1mo ago), licensed MIT. It adds 266 tokens to every session and 3,010 once invoked, about $0.0013 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…