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 skills add alvinindra/figma-mcp-rust --skill bulk-renamegit clone --depth 1 https://github.com/alvinindra/figma-mcp-rustWrote 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/skills/alvinindra/figma-mcp-rust/bulk-rename)<a href="https://agentmods.dev/skills/alvinindra/figma-mcp-rust/bulk-rename"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/bulk-rename/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alvinindra/figma-mcp-rust/bulk-rename"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/bulk-rename.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00639 |
| Opus 5 | $0.00031 | $0.00319 |
| Sonnet 5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
bulk-rename 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 11d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bulk Rename Strategy
Systematically rename nodes to follow a consistent naming convention without moving or modifying any visual properties.
Naming Convention (BEM-style, adapt as needed)
- Screens / pages: "ScreenName" (PascalCase)
- Section frames: "Section/Name"
- Component instances: "ComponentName" (match main component name)
- Containers: "ComponentName/Container"
- Content groups: "ComponentName/Content"
- Interactive elements: "ComponentName/ActionName" (e.g. "Card/CTAButton")
- Text nodes: "Label", "Title", "Body", "Caption"
- Icon wrappers: "Icon/IconName"
- Auto-generated Figma names to avoid: "Frame 123", "Rectangle 45", "Group 6"
Steps
-
Understand the scope Ask the user: rename the entire page, a specific frame, or just selected nodes?
- Entire page: use get_document() to get the root node ID, then scan_nodes_by_types().
- Specific frame: use get_node(nodeId) to inspect it first.
- Selection: use get_selection().
-
Scan target nodes Call scan_nodes_by_types(nodeId, types=["FRAME","GROUP","INSTANCE","TEXT","RECTANGLE","ELLIPSE","VECTOR"]) to get a flat list of all nodes in scope.
-
Identify nodes needing rename Flag nodes whose names match Figma's auto-generated patterns:
- "Frame \d+", "Rectangle \d+", "Group \d+", "Ellipse \d+", "Vector \d+", "Component \d+"
- Any name the user considers non-descriptive.
-
Propose names For each flagged node, derive a new name from:
- Its node type and content (TEXT nodes: use their text content as label).
- Its position in the hierarchy (child of "Card" frame: "Card/...").
- Its visual role (if it contains only an icon: "Icon/...").
- For INSTANCE nodes: use the mainComponent name. Show a preview table to the user before applying: | Node ID | Current Name | Proposed Name |
-
Apply renames (after user confirmation) Call rename_node(nodeId, name) for each node. Process in batches; do not wait for user confirmation between individual renames once the full plan is approved.
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.
- 11d ago First seen · 59 lines · 62 tokens per session scan A 65e3cac4a424
bulk-rename is a skill published in the GitHub repository alvinindra/figma-mcp-rust (38 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 639 once invoked, about $0.0003 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 skills, from other repositories
clean-interface-design
Design clean, calm, uncluttered interfaces that don't read as templated AI output. Use when building or restyling any UI (web, iOS, Android, macOS) and it needs visual hierarchy, restraint, spacing discipline, one clear primary action, and a cohesive look. Covers accent color, whitespace, corner radius, type scale…
landing-page-conversion
Build or improve landing pages and marketing sites that convert, not just look good. Use when writing a hero, structuring a page, choosing a CTA, adding social proof, or diagnosing why a page isn't converting. Covers positioning, copy-first workflow, the above-the-fold contract, page narrative, CTAs, trust, and…
ship-quality-gate
Run the deterministic auditors over a real project before it ships — design drift, security headers, generated-default tells, SEO/GEO signals, delivery signals, Apple and Android project configuration — and read the results correctly, disclosure list included. Use when someone asks "audit this", "is this ready to…
apple-platform-design
Design iOS, iPadOS, and macOS apps that feel native, in the Liquid Glass era. Use when building or reviewing Apple-platform UI — navigation, controls, sheets, materials, typography, haptics — or deciding what must change when porting from web/Android. Covers Apple's HIG, the Liquid Glass design language (iOS 26 /…
saglitzdesign
Design, redesign, build, restyle, improve, critique, review, audit, simplify, polish, or animate a user interface — the front door into SaglitzDesign's eight design skills, for whichever one the work actually needs. Covers landing pages, marketing sites, dashboards, app screens, components, forms, onboarding, empty…
design-review
Critique a UI (screenshot, live page, or code) like a rigorous senior designer — grounded, reproducible, element-citing, and ranked by severity. Use when someone asks "review this design", "what's wrong with this screen", or wants feedback on a mockup/site/app. Avoids the failure modes of typical AI critique…