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 memi-design/design-skills --skill figma-auditgit clone --depth 1 https://github.com/memi-design/design-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/memi-design/design-skills/figma-audit)<a href="https://agentmods.dev/skills/memi-design/design-skills/figma-audit"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-audit/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/memi-design/design-skills/figma-audit"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-audit.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.00022 | $0.01149 |
| Opus 5.5 | $0.00009 | $0.00460 |
| Sonnet 5.5 | $0.00004 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
figma-audit 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-audit — Design System Audit & Quality Check
Audit a Figma file for design system consistency, accessibility compliance, token adoption, and Code Connect coverage. Produces actionable findings. Requires /figma-use.
Freedom Level: Read-Only + Report
Audit skills read and analyze but do not modify the canvas. Output is a structured report with severity levels.
When to Use
- Before a design handoff to development
- After pulling a design system (
memi pull) - Periodic design system health checks
- When components look inconsistent or broken
- Before establishing Code Connect mappings
Audit Checklist
1. Token Adoption
figma_get_variables → list all defined tokens
get_design_context for each page → check usage
Report:
✓ Bound to variable: colors/primary/500
✗ Raw hex: #3b82f6 (should be colors/primary/500)
✗ Magic number: 16px padding (should be spacing/4)
Metric: % of visual properties bound to variables
Target: 90%+
2. Component Consistency
figma_search_components → list all components
figma_get_component_details for each → check structure
Report:
✓ Auto Layout applied
✓ Properties documented
✓ Variants complete (default, hover, active, disabled, focused)
✗ Missing state: Button has no "loading" variant
✗ Inconsistent padding: Card uses 16px, CardHeader uses 12px
Metric: % of components with all required states
Target: 100% for atoms, 90% for molecules
3. Atomic Design Compliance
Check each component's classification:
✓ Atom: no nested component instances (correct)
✗ Atom: Button contains Icon instance (should be molecule or use instance swap)
✓ Molecule: FormField composes Label + Input + HelpText
✗ Organism: LoginForm classified as molecule (too complex)
Metric: % of components correctly classified
Target: 95%+
4. Accessibility
For each component:
✓ Contrast ratio: text on background meets WCAG AA (4.5:1)
✗ Touch target: Button is 32px tall (needs 44px minimum)
✓ Focus indicator: visible focus ring
✗ Missing: no aria-label on icon-only button
For each page:
✓ Heading hierarchy: h1 → h2 → h3 (no skips)
✗ Missing landmark: no main content area defined
✓ Color not sole indicator: error states use icon + color
Metric: WCAG violations per page
Target: 0 critical, <5 minor
What ships with it
1 file 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 · 156 lines · 22 tokens per session scan A 490667b717f0
figma-audit is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,149 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-08-31.
Other skills, from other repositories
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
ai-component-description
Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.
codebase-index
Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.
component-decision-tree
Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.