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/yasuhiro-y/figma-plugin-by-vibe-coding/generate-plugingit clone --depth 1 https://github.com/yasuhiro-y/figma-plugin-by-vibe-codingWrote 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/yasuhiro-y/figma-plugin-by-vibe-coding/generate-plugin)<a href="https://agentmods.dev/commands/yasuhiro-y/figma-plugin-by-vibe-coding/generate-plugin"><img src="https://agentmods.dev/badge/commands/yasuhiro-y/figma-plugin-by-vibe-coding/generate-plugin.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.00017 | $0.01468 |
| Opus 5 | $0.00009 | $0.00734 |
| Sonnet 5 | $0.00003 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
generate-plugin 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Based on the user's request for a new plugin feature, generate a complete implementation that follows our established patterns:
Analysis Phase
- Understand the feature requirements
- Identify required Figma API operations
- Determine necessary shadcn/ui components
- Plan error handling and user feedback
CRITICAL: Demo Code Cleanup First
MANDATORY: Before implementing any new features, remove ALL demo/boilerplate code:
CRITICAL: Update Project Identity After Cleanup
MANDATORY: After removing demo code, STOP and prompt the user to update their project identity:
🚨 STOP! Update your plugin's identity for your actual project.
Your plugin idea is: [USER_PLUGIN_IDEA_DESCRIPTION]
Please confirm you want to update:
1. 📝 Plugin name in figma.manifest.ts → Replace "Figma Plugin by Vibe Coding"
2. 📦 Project name in package.json → Replace "figma-plugin-by-vibe-coding"
3. 🎯 Plugin description in package.json → Describe your actual functionality
4. 🆔 Verify plugin ID is unique (keep generated ID if using create command)
5. 📁 Consider renaming project folder to match your plugin
Type "YES UPDATE IDENTITY" to proceed with identity updates.
DO NOT START FEATURE IMPLEMENTATION until project identity is updated.
CRITICAL: Design Fresh UI from Scratch
MANDATORY: NEVER copy demo UI layouts. Design completely fresh UI optimized for the user's specific plugin functionality.
🚨 UI Design Warning:
🚨 CRITICAL: The demo UI layout is NOT suitable for your plugin!
Current demo: Random Shape Generator layout (header, single card, centered button)
Your plugin: [SPECIFIC_PLUGIN_FUNCTIONALITY]
REQUIRED Actions:
1. 🗑️ DELETE entire demo App.tsx layout structure
2. 🎨 ANALYZE your plugin's workflow and user needs
3. 📐 DESIGN optimal layout using appropriate shadcn/ui patterns
4. 🎯 OPTIMIZE for your specific feature requirements
DO NOT copy demo header, card structure, or button layouts!
✅ Fresh UI Design Process:
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.
- 4d ago First seen · 209 lines · 17 tokens per session scan A 2544a56b097b
generate-plugin is a command published in the GitHub repository yasuhiro-y/figma-plugin-by-vibe-coding (4 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,468 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-31.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
review
執行 Figma vs 網頁的視覺比對審查，產出像素級 diff 報告和 AI 視覺判斷。.