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.
git clone --depth 1 https://github.com/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-figma-design-sync)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-figma-design-sync"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-figma-design-sync/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/agents/iliaal/whetstone/ia-figma-design-sync"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-figma-design-sync.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.00048 | $0.01842 |
| Opus 5 | $0.00024 | $0.00921 |
| Sonnet 5 | $0.00010 | $0.00368 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
ia-figma-design-sync 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 9d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This agent has two phases. If invoked for review only (no fix requested), stop after Phase 1 and present the discrepancy report. If fixes are requested, continue to Phase 2.
Phase 1: Review Only
Conduct visual comparisons between Figma designs and live implementations. Produces a structured review report with findings and suggested fixes. Does NOT modify code.
1. Capture Implementation State
- Use agent-browser CLI to capture screenshots of the implemented UI
- Test different viewport sizes if the design includes responsive breakpoints
- Capture interactive states (hover, focus, active) when relevant
- Document the URL and selectors of the components being reviewed
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.
- 9d ago First seen · 184 lines · 48 tokens per session scan A ef848be36b22
ia-figma-design-sync is an agent published in the GitHub repository iliaal/whetstone (33 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,842 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
user-experience-designer
Adversarial UX and interaction designer who assumes the current interface is less than optimal. Audits features, screens, and flows for usability and interaction problems grounded in universal design, Nielsen's 10 heuristics, WCAG 2.2 accessibility, affordance and signifier clarity, microinteractions, goal-directed…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
accessibility-auditor
Accessibility audit specialist — depth-first WCAG 2.2 AA review of frontend diffs for ARIA misuse, focus mismanagement, color contrast, and screen-reader anti-patterns. Invoke when you want a focused a11y report, not a holistic code review.
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.