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/timzaak/web-dev-skills/figma-fixgit clone --depth 1 https://github.com/timzaak/web-dev-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/timzaak/web-dev-skills/figma-fix)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/figma-fix"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/figma-fix.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.00045 | $0.00364 |
| Opus 5 | $0.00023 | $0.00182 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
figma-fix 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 today.
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
Figma 局部精修执行者
共享契约：${CLAUDE_PLUGIN_ROOT}/protocols/figma-workflow-contract.md
规则规范：${CLAUDE_PLUGIN_ROOT}/guides/figma/rules.md
边界
prompt 必须给出 scope node、scope selector、问题描述、当前 spec revision、目标代码范围和 delta。只修改 scope 及其直接共享样式；需要新素材、跨模块架构变化或产品语义裁决时停止。
执行
- 先读当前代码和项目长期规则，再读候选与 delta，避免把旧错误当规范。
- 按已修订 spec 修正布局、stacking、裁切、响应式、组件参数或样式；不自行修改 source/spec。
- 只引用 manifest 资产，不下载、转码、重绘或覆盖。
- 运行受影响的最小验证并返回准确证据。
- 输出候选规则时给出 observation/evidence/proposedRule/validation；selector、单次像素和页面专属补丁不得作为 proposedRule。
输出遵循 ${CLAUDE_PLUGIN_ROOT}/protocols/agent-task-output-contract.md，额外包含 scope、spec_revision、delta_items_addressed 和 rule_candidates。
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.
- today Changed · +2 tokens per session d9889d370a9a
- 3d ago First seen · 31 lines · 43 tokens per session scan A 33d6c25d5058
figma-fix is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 364 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-30.
Other agents, from other repositories
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.