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 equinor/fusion-skills --skill fusion-researchgit clone --depth 1 https://github.com/equinor/fusion-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/equinor/fusion-skills/fusion-research)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-research"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-research/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/equinor/fusion-skills/fusion-research"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00112 | $0.01761 |
| Opus 5 | $0.00056 | $0.00881 |
| Sonnet 5 | $0.00022 | $0.00352 |
| Haiku 4.5 | $0.00011 | $0.00176 |
Grade A, and why
fusion-research 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion Research
When to use
Use this skill when a user needs a source-backed answer about the Fusion ecosystem.
Typical triggers:
- "Research this Fusion Framework hook and show me the supporting source."
- "What props does this EDS component accept?"
- "Which skill handles X in a Fusion workflow?"
- "Find a source-backed example for…"
- "Which Fusion package or module owns this API?"
- "Is there an EDS design token for this value?"
- "How can I persist user preferences in a Fusion app?"
- "What's the recommended pattern for X in Fusion?"
- "Show me a Fusion Framework example for building X."
- "What are the design tokens for color and spacing in EDS?"
- "How does Fusion handle X at the platform level?"
- "What is the Fusion platform guidance on Y?"
- "How do I onboard to Fusion?"
- "What are the guidelines for Z in the Fusion platform?"
When not to use
Do not use this skill for:
- implementing code changes — use
fusion-app-react-devor the relevant dev skill; if the research is for a specific app you are actively building, usefusion-app-react-devfirst — it will call this skill when needed - finding, installing, updating, or removing skills — use
fusion-discover-skills; use this skill only to understand a skill's scope, relationships, or catalog fit — not to discover what to install - creating or editing skill files — use
fusion-skill-authoringfor authoring-time research - Fusion MCP installation or troubleshooting — use
fusion-mcp; once MCP is running, return here for research - pure conceptual Fusion questions with no specific artifact name (hook, component, package, token, or platform topic) — ask the user for a concrete artifact reference or platform topic first
Instructions
Step 0 — Sharpen scope (optional)
Before classifying, you may use the domain-specific follow-up questions to narrow the user's exact need:
- Framework scope: assets/framework.follow-up.md
- EDS scope: assets/eds.follow-up.md
- Skills catalog scope: assets/skills.follow-up.md
- Docs scope: assets/docs.follow-up.md
What ships with it
16 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.
- agents/backend-code.agent.md 3.2 KB
- agents/docs.agent.md 2.9 KB
- agents/eds.agent.md 2.2 KB
- agents/framework.agent.md 2.4 KB
- agents/skills.agent.md 3.3 KB
- assets/docs.follow-up.md 1.2 KB
- assets/eds.follow-up.md 1.2 KB
- assets/framework.follow-up.md 1.3 KB
- assets/skills.follow-up.md 1.2 KB
- assets/source-backed-answer-template.md 1.1 KB
- CHANGELOG.md 4.7 KB
- references/backend-code.query.md 5.8 KB
- references/docs.query.md 1.6 KB
- references/eds.query.md 1.3 KB
- references/framework.query.md 1.9 KB
- references/skills.query.md 1.5 KB
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 · 136 lines · 112 tokens per session scan A e670373c5744
fusion-research is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session and 1,761 once invoked, about $0.0006 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…