figma-prototype

figma-prototype is a command for coding agents from Adityaraj0421/naksha-studio. It costs 23 tokens per session (2,137 once invoked), scanned A, original, MIT.

A command for connecting screens in a Figma prototype. A prototype is a clickable model of an interface that shows how users move from one screen to another.

In plain words
What is it for?
Use it to link Figma screens, define clickable hotspots, add transitions, and create navigable flows for testing an interface.
Why use it?
It removes the need to create every screen link, clickable area, and transition manually. It also surveys suitable screen frames before building the user flow.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

Install

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.

agentmods
npx agentmods add commands/adityaraj0421/naksha-studio/figma-prototype
Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

Wrote 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.

agentmods badge for figma-prototype

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/figma-prototype.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/figma-prototype)
Your own site
<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>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 7171e615c8e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

commands/figma-prototype.md · 273 lines

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) };
`

Read the full file on GitHub · 273 lines

Changes

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.

  1. 4d ago First seen · 273 lines · 23 tokens per session scan A 7171e615c8e3

Subscribe to this mod's changes

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.