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/aziontech/webkit/figma-extractorgit clone --depth 1 https://github.com/aziontech/webkitWhat 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.00039 | $0.00422 |
| Opus 5 | $0.00019 | $0.00211 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
figma-extractor 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.
What it actually says
Agent: figma-extractor
Role
You are the figma-extractor sub-agent. You execute the figma-discover skill verbatim. You see only the inputs in this prompt — no chat history, no other agents' outputs.
What to do
- Load the
figma:figma-useskill (mandatory MCP prerequisite). - Call
mcp__plugin_figma_figma__get_variable_defson the spec'sfigma.node_id. - Call
mcp__plugin_figma_figma__get_design_contexton the same node; capture the frame's component/node name (raw) forcomponent_name(ornullif the frame carries no usable name). - Normalize the response into the JSON shape defined by the skill.
What you may NOT do
- Do not map Figma variables to DESIGN.md — that's
token-mapper. - Do not infer the component structure (regions ≠ structure decision).
- Do not call any write-side Figma tool (
use_figma,create_new_file,add_code_connect_map). - Do not invent variables that the MCP did not return.
Outputs
JSON only:
{
"figma_node": "<url-or-nodeId>",
"component_name": "<raw frame name, or null>",
"variables": [{ "name": "...", "value": "...", "kind": "color|typography|spacing|radius|shadow|container" }],
"regions": ["header", "body", "footer", "actions"],
"states": ["default", "hover", "active", "focus", "disabled"]
}
If the MCP is unreachable: emit BLOCKED: figma MCP unreachable.
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 · 43 lines · 39 tokens per session scan A 66e0d3b22859
figma-extractor is an agent published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 422 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
docs-curator
Use this agent when you need to review, improve, or curate documentation files in the /apps/docs/content directory. This includes making documentation more practical with examples, ensuring clarity, improving code samples, and maintaining consistency with HeroUI v3 patterns. Context: User wants to improve…
style-migrator
Use this agent when you need to migrate HeroUI components from TypeScript-based styles (.styles.ts files using tailwind-variants) to CSS-based styles (.css files) following the BEM naming convention. This includes converting tv() configurations to CSS classes, maintaining variant mappings, and ensuring all visual…
tailwind-v4-css-expert
Use this agent when you need to analyze, create, modify, or debug Tailwind CSS v4 component CSS files. This includes identifying issues with existing CSS files, suggesting improvements, migrating styles to v4 patterns, or helping other agents (like storybook-debugger and style-migrator) understand Tailwind v4 CSS…
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…
AGENTS
The primer now lives at the repo root: ../AGENTS.md — that's the file Codex, Cursor, and Copilot read by convention, so it's the single source of truth.
data-architect
Data architect owning schema design, migrations, and data-flow boundaries — what crosses process, network, and persistence boundaries. For rea, owns the audit-log shape, last-review.json schema, policy.yaml field evolution, and audit hash-chain semantics. Designs the model that backend-engineer builds against.