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 n-n-code/n-n-code-skills --skill fuse-skillsgit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/fuse-skills)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/fuse-skills"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/fuse-skills.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.00092 | $0.02438 |
| Opus 5 | $0.00046 | $0.01219 |
| Sonnet 5 | $0.00018 | $0.00488 |
| Haiku 4.5 | $0.00009 | $0.00244 |
Grade A, and why
fuse-skills 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fuse Skills
Create one coherent skill package from multiple bounded sources. Fusion is a transfer of semantic ownership, not a paste-and-trim exercise: every in-scope trigger, capability, externally visible output, and resource needs an owner after the change; every source needs a classification, and every destination-managed source package needs an explicit action.
Inputs and defaults
Bound the source set before analysis. Accept:
- exact local skill names or paths;
- complete skill content supplied inline;
- exact remote skill locators, preserving any revision and subpath;
- a named remote package whose intended skill or skills can be resolved without searching unrelated packages; or
- a bounded local family that can be resolved from local folders only.
Do not broaden into general skill discovery. If a family or package contains multiple materially different candidates and the user's intent does not select among them, pause with the candidate set and the decision needed.
Treat review and design requests as destination- and source-package read-only; permission-bound network retrieval and an owned disposable checkout remain allowed when needed to inspect an in-scope remote source. A clear request to create, fuse, or update authorizes target-package writes, but not changes to separate source packages. Default to a new target and leave every source unchanged; revising an explicitly named target is allowed. If no target name is supplied, choose a narrow, meaningful name under the destination's conventions and report it. If the destination supplies no contrary evidence, prefer portable semantics over repo-bound or host-specific behavior.
Renaming, narrowing, retiring, unpublishing, or removing a separate source requires explicit authority. If a union-style target would materially overlap retained sources and no package is authorized to surrender that trigger, present one topology decision before writing. A review may propose an unregistered draft, but do not publish active packages with ambiguous ownership.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 211 lines · 92 tokens per session scan A 6aaa07045f02
fuse-skills is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 2,438 once invoked, about $0.0005 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
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".