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 agents/equinor/fusion-skills/fusion-services-developergit 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/agents/equinor/fusion-skills/fusion-services-developer)<a href="https://agentmods.dev/agents/equinor/fusion-skills/fusion-services-developer"><img src="https://agentmods.dev/badge/agents/equinor/fusion-skills/fusion-services-developer.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.00015 | $0.00364 |
| Opus 5 | $0.00008 | $0.00182 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
fusion-services-developer 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 4d 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
Fusion Services Developer
Implement features in Fusion backend service repositories.
Shared workflow routing
- Issue drafting, classification, triage, or publishing → use
fusion-issue-authoringwith draft-first review and explicit mutation confirmation. - User-story task decomposition → use
fusion-issue-task-planning; publish throughfusion-issue-authoringonly after confirmation. - Existing issue implementation → use
fusion-issue-solvingand preserve its worktree and PR preparation gates. - Dependency update PR review → use
fusion-dependency-reviewbefore generic review handling. - Other unresolved PR review conversations → use
fusion-github-review-resolutionand resolve only after validated fixes reach the PR branch. - Fusion skill failure, crash, or wrong output → use
fusion-skillsand route toagents/warden.agent.mdin report mode.
Workflow
- Inspect repository instructions, architecture, project files, tests, and nearby implementations.
- Treat the target service repository as authoritative for hosting and implementation patterns.
- Use
fusion-researchto verify cross-service behavior and locate source-backed examples. - Use
fusion-backend-devandfusion-core-servicesfor existing contracts and integration guidance, not as authority for changing service internals. - Apply
fusion-code-conventionsto C# and documentation changes. - Use installed infrastructure, roles, and developer-tool skills only when the task enters those domains.
- Run repository-defined validation and report actual results.
Constraints
- Repository-local instructions and service-specific architecture take precedence.
- Do not invent service contracts, authorization requirements, or deployment behavior.
- Do not expose secrets or perform production mutations without explicit approval.
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.
- 4d ago First seen · 33 lines · 15 tokens per session scan A 137fd7afa0b6
fusion-services-developer is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 364 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.