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 fusengine/agents --skill design-methodgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/design-method)<a href="https://agentmods.dev/skills/fusengine/agents/design-method"><img src="https://agentmods.dev/badge/skills/fusengine/agents/design-method/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/fusengine/agents/design-method"><img src="https://agentmods.dev/badge/skills/fusengine/agents/design-method.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 507 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00035 | $0.11241 |
| Opus 5.5 | $0.00014 | $0.04496 |
| Sonnet 5.5 | $0.00007 | $0.02248 |
| Haiku 4.5 | $0.00003 | $0.01124 |
Grade A, and why
design-method 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 8d 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 — 564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read this first — before design-system, any register/*.md file, or any moves/*.md file. This skill owns the gate and the routing table, not the move procedures themselves.
Design Method — The Core
This is the one place the design pipeline is defined. The agent (agents/design-expert.md)
always loads this file before dispatching to a move; every references/register/*.md and
references/moves/*.md file assumes you've read this first and references it instead of
restating it — if a rule elsewhere contradicts this file, this file wins.
Setup
How this core gets loaded, every time, no exceptions:
- Read this file once per task — not once per move. Skip the re-read for a later move in the same task if neither the Register nor the codebase changed.
- Read
../design-system/SKILL.md— always, unconditionally, before anything else below. Thin pointer file, cheap to reload, and the harness's phase-1 trigger, so it runs even on a task needing no new token. Existingdesign-system.mdtokens still win over its defaults once resolved. - Resolve Register (below), then write the Design Read + 3 dials one-liner.
- Pass Gate 0 — Brief Lock (below) before touching any HTML/CSS/tokens.
- Read the ONE matched
references/moves/<move>.mdfrom the Routing table — not two, not a skim of several to "compare." The move file owns the how; this file owns the gate and the pointer. - If the move builds or touches code, read the matching
references/register/{brand,product}.mdfloors too, once.
What ships with it
14 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.
- references/body-sequence-bank.md 21 KB
- references/macrostructure-bank.md 4.5 KB
- references/moves/audit.md 4.1 KB
- references/moves/bolder.md 2.7 KB
- references/moves/critique.md 3.5 KB
- references/moves/distill.md 3.0 KB
- references/moves/generate.md 23 KB
- references/moves/harden.md 2.5 KB
- references/moves/polish.md 2.3 KB
- references/moves/quieter.md 2.8 KB
- references/moves/redesign.md 9.0 KB
- references/register/brand.md 7.4 KB
- references/register/copy.md 5.6 KB
- references/register/product.md 5.0 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.
- 8d ago Changed 7d23e8d706d8
- 23d ago Changed 8d711eab66d6
- 1mo ago First seen · 564 lines · 35 tokens per session scan A cf0dc9fcd69e
design-method is a skill published in the GitHub repository fusengine/agents (33 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 11,241 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
designing-interfaces
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
visual
Define a brand's visual identity — logo usage rules and variations, a color palette with contrast ratios, typography and type scale, and photography, illustration and icon style. Use when the user needs to settle their brand colors, fonts, logo rules or imagery style, or formalize the visual assets they already have.
a11y-audit
Audit a Figma component or frame for accessibility in one pass — design lint, contrast, color-blindness simulation, focus order — with fixes. Use when the user points at a Figma design and wants a quick accessibility check before it goes to development. Not for a full WCAG-EM audit of a built site or app, or mentoring…
design-review
Create a Figma Slides deck summarizing a component's design journey — research, contract, options, prototype and test results — with title and summary slides. Use when the user needs to present a component's design work to stakeholders or walk a team through it. Not for feedback on a design; see /coaching:ux or…
export-tokens
Export the design tokens (variables) from a Figma file as CSS custom properties, Tailwind config or JSON, optionally saved to a file. Use when the user wants Figma colors, spacing and type values in code, or gives a Figma URL and asks for its tokens. Not for an inventory of the whole design system; see…
system-overview
Summarize a Figma file's design system — components, styles, token collections and modes, and page structure — in one structured overview. Use when the user is new to a Figma design system or wants to know what it contains before working with it. Not for exporting tokens as code; see /design:export-tokens.