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-syncgit 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-sync)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma-sync"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma-sync.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.02105 |
| Opus 5 | $0.00012 | $0.01052 |
| Sonnet 5 | $0.00005 | $0.00421 |
| Haiku 4.5 | $0.00002 | $0.00211 |
Grade A, and why
figma-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 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.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-sync
You are performing a design-code sync check — comparing a Figma file's design tokens, components, and visual properties against the codebase to detect drift.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/figma-creation.md for Figma API patterns and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/design-system-lead.md for token architecture.
Process
1. Connect & Detect Context
figma_get_status → verify Desktop Bridge connection
Detect the code stack:
- Look for
tailwind.config.*,postcss.config.*→ Tailwind - Look for
*.csswith--custom-properties→ CSS custom properties - Look for
tokens.json,*.tokens.*→ Design token files - Look for
package.json→ framework detection (React, Vue, Svelte, Next.js)
2. Extract Figma Design Tokens
Colors
figma_execute: `
const styles = await figma.getLocalPaintStylesAsync();
return styles.map(s => {
const fill = s.paints[0];
let hex = null;
if (fill?.type === 'SOLID') {
const c = fill.color;
hex = '#' + [c.r, c.g, c.b].map(v => Math.round(v * 255).toString(16).padStart(2, '0')).join('');
}
return { name: s.name, hex, opacity: fill?.opacity };
});
`
Typography
figma_execute: `
const styles = await figma.getLocalTextStylesAsync();
return styles.map(s => ({
name: s.name,
fontFamily: s.fontName?.family,
fontWeight: s.fontName?.style,
fontSize: s.fontSize,
lineHeight: s.lineHeight,
letterSpacing: s.letterSpacing
}));
`
Variables / Tokens
figma_execute: `
const collections = await figma.variables.getLocalVariableCollectionsAsync();
const result = [];
for (const col of collections) {
const vars = [];
for (const id of col.variableIds) {
const v = await figma.variables.getVariableByIdAsync(id);
vars.push({
name: v.name,
type: v.resolvedType,
values: v.valuesByMode
});
}
result.push({ collection: col.name, modes: col.modes, variables: vars });
}
return result;
`
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 · 271 lines · 23 tokens per session scan A 1ae39c8e58bd
figma-sync 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,105 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
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).
remix
Restyle a site in another design vocabulary — brutalist, swiss, art-deco, cyberpunk, soft-ui, or editorial. Preserves page shape, swaps the visual vocabulary.
studio
Launch the local design Studio — a live token editor over the latest extraction. Edit, preview a wall of real components, toggle dark mode, inspect motion, and export.
full-diagnostic
Comprehensive design system health sweep.
release-check
Pre-release validation pipeline for a component.
describe-component
Generate an AI-optimised component description.