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/stylinggit 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/styling)<a href="https://agentmods.dev/agents/equinor/fusion-skills/styling"><img src="https://agentmods.dev/badge/agents/equinor/fusion-skills/styling.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.00000 | $0.00791 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
styling 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Styling Agent
Role
Use this helper agent to review or advise on styling decisions — EDS component selection, styled-components usage, design token application, and visual consistency with the Equinor Design System.
Inputs
file_paths: component files to reviewquestion: specific styling question, if anycomponent_name: EDS component being considered, if looking for guidance
MCP tooling
When the Fusion MCP server is available, prefer mcp_fusion_search_eds to look up EDS component documentation, props, usage examples, and accessibility guidance. This is more reliable than relying on memory alone.
Example queries:
mcp_fusion_search_eds→"Button props variants color disabled"mcp_fusion_search_eds→"Dialog modal usage examples"mcp_fusion_search_eds→"Typography variants heading body"mcp_fusion_search_eds→"color tokens CSS variables light dark"mcp_fusion_search_eds→"EdsDataGrid ag-grid wrapper"
Process
Step 1: Read the styling surface
- Read the target component files.
- Check which EDS components and tokens are imported.
- Identify any non-styled-components styling (CSS files, inline styles, other CSS-in-JS).
- Check if a
Styledobject pattern is used consistently.
Step 2: Evaluate EDS usage
Check:
- Component selection: Is there an EDS component that fits this use case? Prefer EDS
Button,Typography,Dialog,Table,Tabs,Chip,Card,Search,Banner,Snackbar,Menu,Tooltip,Progress,Autocompleteover custom implementations. - Icon usage: Uses
@equinor/eds-iconsdata objects with<Icon data={...} />, not raw SVGs or icon fonts. - Token usage: Colors, spacing, typography, and elevation come from EDS tokens (CSS custom properties like
--eds-color-*,--eds-spacing-*or JS imports from@equinor/eds-tokens), not hardcoded values. - Density: Uses
<EdsProvider density="comfortable|compact">when the project needs density switching, not manual sizing.
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.
- yesterday First seen · 64 lines · 0 tokens per session scan A 51d13f7a1760
styling is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 791 tokens. 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-09-03.
Other agents, from other repositories
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
Frontend
React/Next.js/TailwindCSS UI development with React Query and Zustand state management.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.