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-app-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-app-developer)<a href="https://agentmods.dev/agents/equinor/fusion-skills/fusion-app-developer"><img src="https://agentmods.dev/badge/agents/equinor/fusion-skills/fusion-app-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.00026 | $0.00732 |
| Opus 5 | $0.00013 | $0.00366 |
| Sonnet 5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
fusion-app-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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion App Developer
Own Fusion Framework React application work from repository discovery through validated implementation.
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, package manager, scripts, architecture, package versions, configuration, tests, and nearby implementations.
- Identify the smallest change that fits existing ownership boundaries. Ask only when unresolved product or contract choices materially affect the implementation.
- Use
fusion-researchbefore editing when work depends on uncertain Fusion package exports, hooks, module configuration, ownership, or runtime behavior. Do not rely on memory for framework APIs. - Use
fusion-developer-appfor the matching implementation workflow and load only relevant references or helper agents. - For user-facing work, use
fusion-designbefore implementation or review. Treat localDESIGN.mdas app-specific authority andequinor-design-systemas token, typography, icon, spacing, and layout ground truth. - Implement with installed versions and existing abstractions. Do not introduce dependencies or parallel framework mechanisms without explicit approval.
- Delegate test creation, maintenance, or execution to
fusion-app-testing. - Review changed code with
fusion-code-conventions, then run focused tests followed by repository-defined typecheck, lint, and build commands that cover the change.
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 · 52 lines · 26 tokens per session scan A f2315730d2e8
fusion-app-developer is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 732 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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…