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 sahajamit/figma-cli --skill figma-designgit clone --depth 1 https://github.com/sahajamit/figma-cliWrote 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/sahajamit/figma-cli/figma-design)<a href="https://agentmods.dev/skills/sahajamit/figma-cli/figma-design"><img src="https://agentmods.dev/badge/skills/sahajamit/figma-cli/figma-design/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/sahajamit/figma-cli/figma-design"><img src="https://agentmods.dev/badge/skills/sahajamit/figma-cli/figma-design.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.00031 | $0.01431 |
| Opus 5.5 | $0.00012 | $0.00572 |
| Sonnet 5.5 | $0.00006 | $0.00286 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
figma-design 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 2mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
figma — Design System Commands
Quick start
# List components
figma components list <file-key>
# Search for a component
figma components search <file-key> --query Button
# List styles
figma styles list <file-key>
# Get design variables
figma variables list <file-key>
# Export design tokens (W3C format)
figma tokens export <file-key> --json
figma components list <file-key>
List components in a file.
figma components list <file-key> [--json]
JSON output:
{
"meta": {
"components": [
{ "key": "abc", "node_id": "1:2", "name": "Button/Primary", "description": "..." }
]
}
}
figma components search <file-key>
Search components by name (case-insensitive).
figma components search <file-key> --query <text> [--json]
JSON output: Array of matching component objects.
figma components team <team-id>
List published team components.
figma components team <team-id> [--json]
figma styles list <file-key>
List styles in a file.
figma styles list <file-key> [--json]
JSON output:
{
"meta": {
"styles": [
{ "key": "abc", "node_id": "1:2", "style_type": "FILL", "name": "Primary/500", "description": "..." }
]
}
}
figma styles team <team-id>
List published team styles.
figma styles team <team-id> [--json]
figma variables list <file-key>
List local variables (design tokens from Figma's native variables).
figma variables list <file-key> [--json]
Note: Requires
file_variables:readscope on your token.
JSON output:
{
"meta": {
"variableCollections": { "id": { "name": "Colors", "modes": [...], "variableIds": [...] } },
"variables": { "id": { "name": "primary", "resolvedType": "COLOR", "valuesByMode": {...} } }
}
}
figma tokens export <file-key>
Extract design tokens from a file in W3C Design Tokens Community Group format. Extracts colors, spacing, sizes, typography, and shadows from the node tree.
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.
- 2mo ago First seen · 203 lines · 31 tokens per session scan A 3eac6327419f
figma-design is a skill published in the GitHub repository sahajamit/figma-cli (9 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,431 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.
figma-design compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| figma-designsahajamit/figma-cli | Skill | 9 | 6mo ago | MIT | A | 31 | Claude Code |
| webgl-holographic-foilnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 41 | Claude Code, Codex |
| html-ppt-hermes-cyber-terminalnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 53 | Claude Code, Codex |
| html-ppt-taste-brutalistnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 78 | Claude Code, Codex |
| visual-ralphYeachan-Heo/oh-my-codex | Skill | 34k | 3d ago | MIT | A | 52 | Codex |
| glance-canonical-layoutsandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 56 | Claude Code |
| accessibilitymicrosoft/hve-core | Skill | 1.6k | yesterday | MIT | A | 47 | Claude Code |