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 agentmods add skills/okisdev/claude-code-fusion/smokenpx skills add okisdev/claude-code-fusion --skill smokegit clone --depth 1 https://github.com/okisdev/claude-code-fusionWrote 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/okisdev/claude-code-fusion/smoke)<a href="https://agentmods.dev/skills/okisdev/claude-code-fusion/smoke"><img src="https://agentmods.dev/badge/skills/okisdev/claude-code-fusion/smoke.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 | $0.00025 | $0.00468 |
| Opus 5 | $0.00013 | $0.00234 |
| Sonnet 5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
smoke 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 3d 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
Verify the update landed, then prove the dispatch chain end to end with three tiny probes before real packages ride it.
- Version parity: read
~/.claude/plugins/installed_plugins.jsonand compare the fusion, codex, and grok entries against.claude-plugin/marketplace.jsonin this repository when present. Report each version pair; a mismatch is a FAIL naming the stale plugin. - Fan out three probes as parallel foreground Agent calls in one message: a
codex:codex-rescuetask passing--model gpt-5.6-luna --effort low -- Reply with exactly this single line and nothing else: FUSION-SMOKE-CODEX-OK; agrok:grok-rescuetask whose direct prompt passes--effort low --followed by a brief whose header line isgrok-role: burst | effort low | acceptance: exact marker lineand whose body asks for exactly the line FUSION-SMOKE-GROK-OK; afusion:trivial-workerbrief in thefusion-brief: v1envelope withcontext-mode: isolated, a goal of returning exactly the line FUSION-SMOKE-WORKER-OK, a scope of no file access, and an acceptance of the exact marker line. - Collect all three, then settle them in one
/fusion:stats --recordcall with one pair per probe: accepted only when the exact marker line came back, rejected otherwise. - Report one PASS or FAIL line per gate: version parity, codex dispatch and envelope, grok dispatch and sandbox handshake, worker dispatch and deliverable, settlement write. A FAIL names the failing surface and advises holding real dispatches on that lane until repaired.
The wave is a probe, not work: never attach real packages to it, and never skip the settlement step, because the settlement write is itself one of the gates under test.
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.
- 3d ago First seen · 17 lines · 25 tokens per session scan A 4e147e01f0fa
smoke is a skill published in the GitHub repository okisdev/claude-code-fusion (3 stars, last pushed 16d ago), licensed MIT. It adds 25 tokens to every session and 468 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.