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-creategit 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-create)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma-create"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma-create.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.1 | $0.00021 | $0.01662 |
| Opus 5 | $0.00010 | $0.00831 |
| Sonnet 5 | $0.00004 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
figma-create 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 6d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-create
You are running the Figma-native design creation workflow. Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/figma-creation.md for the complete API and pattern reference.
This command creates designs INSIDE Figma — the reverse of /figma which extracts from Figma to code.
Input: $ARGUMENTS
Process
1. Check Connection
figma_get_status → verify WebSocket Desktop Bridge is connected
If not connected, guide the user:
- Open your Figma file in Figma Desktop
- Right-click canvas → Plugins → Development → Figma Desktop Bridge
- Wait for "Connected" confirmation
- Try
figma_get_statusagain
2. Understand the Task
Parse the user's request to determine what needs to be created:
| Task Type | What to build |
|---|---|
| Page structure | New pages with named frames at specified sizes |
| Wireframes | Mid-fidelity gray layouts with placeholder content |
| Components | COMPONENT_SET with variants (states, sizes, types) |
| Design system | Color styles, text styles, variables/tokens |
| Hi-fi screens | Full-fidelity designed frames with real content |
| Annotations | Leader lines, numbered badges, annotation cards |
3. Read References
Load the knowledge you need based on the task:
- Always:
figma-creation.md(core API patterns) - Components/tokens:
design-system-lead.md(token architecture, naming) - Layout/visual:
ui-designer.md(spacing, typography, color) - Wireframes/flows:
ux-designer.md(information architecture, user flows) - Copy/labels:
content-designer.md(microcopy, naming conventions)
Also activate the Design Manager from SKILL.md to assemble the right specialist roles for the task.
4. Plan the Structure
Before writing any Figma code, define:
- Page names and hierarchy
- Frame sizes (common: 1440×900 desktop, 375×812 mobile, 768×1024 tablet)
- Naming conventions (e.g.,
S3-A,Page 1—Title) - Component taxonomy (what gets componentized vs. one-off frames)
- Style definitions (colors, text styles to create)
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.
- 6d ago First seen · 158 lines · 21 tokens per session scan A 2d42009b30d3
figma-create is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,662 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.
docs-coverage
Audit whether your documentation surface keeps pace with your components.
governance-review
Quarterly governance review package.
release-check
Pre-release validation pipeline for a component.
component-audit
Audit your component library inventory.