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-responsivegit 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-responsive)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma-responsive"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma-responsive.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.00026 | $0.02684 |
| Opus 5 | $0.00013 | $0.01342 |
| Sonnet 5 | $0.00005 | $0.00537 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
figma-responsive 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-responsive
You are generating responsive breakpoint variants from an existing desktop Figma frame. This takes a 1440px (or similar) desktop design and creates mobile (375×812) and/or tablet (768×1024) adaptations directly in Figma.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/figma-creation.md for the Figma API patterns and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ui-designer.md for responsive design principles.
Process
1. Connect & Identify Source Frame
figma_get_status → verify Desktop Bridge connection
Find the source desktop frame:
- If user gave a node ID:
figma.getNodeByIdAsync(id) - If user gave a frame name: search for it
- If neither: ask which frame to adapt
figma_execute: `
const frame = await figma.getNodeByIdAsync('SOURCE_ID');
return {
name: frame.name,
width: frame.width,
height: frame.height,
layoutMode: frame.layoutMode,
childCount: frame.children.length,
children: frame.children.map(c => ({
name: c.name,
type: c.type,
width: c.width,
height: c.height,
layoutMode: c.layoutMode,
layoutSizingH: c.layoutSizingHorizontal,
layoutSizingV: c.layoutSizingVertical
}))
};
`
Screenshot the source for reference:
figma_capture_screenshot(sourceFrameId) → desktop reference
2. Analyze Layout Structure
Map the source frame's layout hierarchy to understand what needs to adapt:
figma_execute: `
async function mapLayout(node, depth = 0) {
const info = {
name: node.name,
type: node.type,
layout: node.layoutMode || 'NONE',
sizing: { h: node.layoutSizingHorizontal, v: node.layoutSizingVertical },
dimensions: { w: Math.round(node.width), h: Math.round(node.height) },
spacing: node.itemSpacing,
padding: node.paddingLeft ? { l: node.paddingLeft, r: node.paddingRight, t: node.paddingTop, b: node.paddingBottom } : null,
childCount: node.children?.length || 0,
children: []
};
if ('children' in node && depth < 3) {
for (const child of node.children) {
info.children.push(await mapLayout(child, depth + 1));
}
}
return info;
}
const source = await figma.getNodeByIdAsync('SOURCE_ID');
return await mapLayout(source);
`
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 · 313 lines · 26 tokens per session scan A baa88868f66b
figma-responsive is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 2,684 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.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.
release-check
Pre-release validation pipeline for a component.