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-framework-testinggit 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-framework-testing)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-framework-testing"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-framework-testing/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-framework-testing"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-framework-testing.svg" alt="Reviewed on agentmods" width="80" 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.00169 | $0.01869 |
| Opus 5.5 | $0.00068 | $0.00748 |
| Sonnet 5.5 | $0.00034 | $0.00374 |
| Haiku 4.5 | $0.00017 | $0.00187 |
Grade A, and why
fusion-framework-testing 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 1mo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion Framework Testing
When to use
Use when writing or running a Vitest test for a Fusion Framework React app — a hook, component, route, or complete app — or when setting up/troubleshooting the test project itself.
Typical triggers:
- "Write a test for this component / hook / route"
- "Set up
vitest.config.tsfor this app" - "Why does this test hang / hit the network / fail to resolve the app?"
- "Should this be a hook test or a component test?"
- "Share seeded fixtures across a test file"
- "Migrate this suite off Testing Library / jsdom"
Implicit triggers:
- A test file imports
@equinor/fusion-framework-vitest-plugin-react-app(or its/test,/configsub-paths) vitest.config.tsneeds Browser Mode, Playwright, or app-file resolution configured- A test renders a component/hook that reads
useAppModule,useFramework, or similar
When not to use
- Seeding module-specific state (a signed-in user, current context, feature flags, HTTP
responses) — use
fusion-framework-mocking; this skill only covers rendering/running the test dev-server.config.tsAPI mocking/proxying for localffc app dev— dev-time only, seefusion-developer-app- Non-Fusion test suites, or backend/service-repo tests
Required inputs
Mandatory
- What is under test: pure function, hook, component, route, or complete app
- Whether the project already has
vitest.config.tsconfigured for this package
Conditional
- Whether the test needs a specific signed-in user, seeded context, or faked HTTP response (then
hand off to
fusion-framework-mockingfor the seeding details) - Whether several test files need the same fixture defaults
Instructions
Step 1 — Choose the smallest layer for the behavior under test
Fusion test utilities substitute external boundaries only; Vitest still owns the runner, assertions, lifecycle hooks, spies, timers, and coverage.
| Testing intent | Start with | Import |
|---|---|---|
| Pure function or framework-independent hook | Standard Vitest | vitest |
| React hook that consumes app modules | renderAppHook |
@equinor/fusion-framework-vitest-plugin-react-app |
| React component, route, or complete app | test/render fixture |
@equinor/fusion-framework-vitest-plugin-react-app/test |
| Reusable app fixture without automatic app-file resolution | testApp |
@equinor/fusion-framework-vitest-plugin-react-app |
| App module configuration without React | mockAppModules |
see fusion-framework-mocking |
| Parent framework or portal-level modules | mockFramework |
see fusion-framework-mocking |
| One method call, timer, global, or JS module | Vitest's vi APIs |
vitest |
What ships with it
5 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.
- 1mo ago First seen · 166 lines · 169 tokens per session scan A 0e6d6a6bbf69
fusion-framework-testing is a skill published in the GitHub repository equinor/fusion-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 169 tokens to every session and 1,869 once invoked, about $0.0007 per session on Opus 5.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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.