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/figmagit 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)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma.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.01483 |
| Opus 5 | $0.00012 | $0.00741 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00002 | $0.00148 |
Grade A, and why
figma scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L "[screenshot.downloadUrl]" -o stitch-reference.png How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma
You are running the Figma-to-code workflow. Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/figma-workflow.md for the complete guide, and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ui-designer.md for visual implementation standards.
Input: $ARGUMENTS
Process
1. Get the Design
Stitch Input (if $ARGUMENTS contains stitch: or stitch )
If the input is a Stitch screen reference (format: stitch:[projectId]/[screenId] or stitch [projectId] [screenId]):
-
Fetch screen details:
mcp__stitch__get_screen( name: "projects/[projectId]/screens/[screenId]", projectId: [projectId], screenId: [screenId] ) -
Download visual reference:
curl -L "[screenshot.downloadUrl]" -o stitch-reference.png -
If
figmaExportis present in the screen response, download it:curl -L "[figmaExport.downloadUrl]" -o stitch-export.figOpen
stitch-export.figin Figma Desktop, then useget_design_contextnormally. Skip to Step 3. -
If only
htmlCodeis available (no figmaExport), download it:curl -L "[htmlCode.downloadUrl]" -o stitch-source.htmlUse
stitch-source.htmlas the implementation base — skip Steps 1–4, go directly to Step 5 (Preview and Compare) usingstitch-reference.pngas the visual target.
Figma URL Input
- If a Figma URL is provided, extract the fileKey and nodeId:
- URL format:
https://figma.com/design/:fileKey/:fileName?node-id=:nodeId - Node ID format in URL uses
-separator, convert to:for API (e.g.,1-2→1:2) - Call
get_design_contextwith the extracted fileKey and nodeId
- URL format:
- If no URL is provided, use the Figma desktop app tools (
get_design_contextwithout parameters) - Also call
get_screenshotto get a visual reference of the target design
2. Check Code Connect
- Call
get_code_connect_mapto see if any components are already mapped to code - If mappings exist, use the mapped component names and sources in your implementation
- This allows reusing existing components rather than rebuilding from scratch
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.
- 5d ago First seen · 139 lines · 23 tokens per session scan A d4247fd53b92
figma 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 1,483 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
release-check
Pre-release validation pipeline for a component.
describe-component
Generate an AI-optimised component description.
docs-coverage
Audit whether your documentation surface keeps pace with your components.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.