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 commands/adityaraj0421/naksha-studio/figma-prototypegit clone --depth 1 https://github.com/Adityaraj0421/naksha-studioWrote 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/commands/adityaraj0421/naksha-studio/figma-prototype)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma-prototype"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma-prototype.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.00023 | $0.02137 |
| Opus 5 | $0.00012 | $0.01069 |
| Sonnet 5 | $0.00005 | $0.00427 |
| Haiku 4.5 | $0.00002 | $0.00214 |
Grade A, and why
figma-prototype 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 4d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-prototype
You are creating interactive prototype connections in Figma — linking screens together with transitions, defining clickable hotspots, and setting up navigable user flows.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/figma-creation.md for Figma API patterns and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ux-designer.md for user flow design.
Process
1. Connect & Survey Screens
figma_get_status → verify Desktop Bridge connection
Get all top-level frames that could be screens:
figma_execute: `
await figma.loadAllPagesAsync();
const pages = figma.root.children.map(p => ({
name: p.name,
frames: p.children
.filter(c => c.type === 'FRAME' && c.width >= 300 && c.height >= 400)
.map(f => ({
id: f.id,
name: f.name,
width: Math.round(f.width),
height: Math.round(f.height)
}))
}));
return pages;
`
2. Identify Interactive Elements
For each screen, find elements that should be clickable:
figma_execute: `
const frame = await figma.getNodeByIdAsync('FRAME_ID');
const interactive = [];
function scan(node) {
const name = node.name.toLowerCase();
const isInteractive =
name.includes('button') || name.includes('btn') ||
name.includes('link') || name.includes('cta') ||
name.includes('nav') || name.includes('tab') ||
name.includes('menu') || name.includes('card') ||
name.includes('icon') || name.includes('arrow') ||
name.includes('back') || name.includes('close') ||
name.includes('next') || name.includes('prev') ||
node.type === 'INSTANCE';
if (isInteractive && node.width > 20 && node.height > 20) {
interactive.push({
id: node.id,
name: node.name,
type: node.type,
width: Math.round(node.width),
height: Math.round(node.height),
x: Math.round(node.absoluteTransform[0][2]),
y: Math.round(node.absoluteTransform[1][2])
});
}
if ('children' in node && node.type !== 'INSTANCE') {
node.children.forEach(scan);
}
}
frame.children.forEach(scan);
return { screen: frame.name, interactiveElements: interactive.slice(0, 30) };
`
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.
- 4d ago First seen · 273 lines · 23 tokens per session scan A 7171e615c8e3
figma-prototype is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 2,137 once invoked, about $0.0001 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 commands, from other repositories
full-diagnostic
Comprehensive design system health sweep.
describe-component
Generate an AI-optimised component description.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.
system-health
Score your design system's overall health.
token-audit
Audit your design token architecture.