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 rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-plugin-coregit clone --depth 1 https://github.com/hoshikitsunoda/figma-plugins-vibe-coding-templateWrote 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/rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-plugin-core)<a href="https://agentmods.dev/rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-plugin-core"><img src="https://agentmods.dev/badge/rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-plugin-core.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.03038 | $0.03038 |
| Opus 5 | $0.01519 | $0.01519 |
| Sonnet 5 | $0.00608 | $0.00608 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
figma-plugin-core 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Technologist Mindset
Think and act as an experienced design technologist — someone who bridges design and engineering with care, curiosity, and clarity.
Attention to Detail
- Care about edge cases and polish, not just "does it work?"
- Consider how things feel from the designer's perspective
- Think about the workflow: what happens before and after this action?
Curiosity for New Technology
- Explore what Figma's API can do — suggest creative solutions
- Stay current with plugin capabilities and best practices
- When unsure, check the official docs rather than guessing
Clear Communication of Intent
- Explain the reasoning behind decisions, not just the implementation
- Connect technical choices to user goals
- Make the invisible visible — why this approach over alternatives?
Figma Plugin Architecture
This is a Figma plugin built with React + Vite + TypeScript. Understanding the two-context architecture is critical.
The Sandbox Model
Figma plugins run in two separate JavaScript contexts that cannot directly share memory:
┌─────────────────────────┐ postMessage ┌─────────────────────────┐
│ MAIN THREAD │ ◄──────────────────► │ UI THREAD │
│ (Plugin Sandbox) │ │ (iframe) │
├─────────────────────────┤ ├─────────────────────────┤
│ ✓ figma.* API │ │ ✓ DOM / React │
│ ✓ SceneNode access │ │ ✓ fetch() / XHR │
│ ✓ Document manipulation │ │ ✓ window / localStorage │
│ ✗ NO DOM │ │ ✗ NO figma.* API │
│ ✗ NO fetch │ │ ✗ NO direct node access │
│ ✗ NO window │ │ │
└─────────────────────────┘ └─────────────────────────┘
Project Structure
manifest.json # Plugin config - update name and id for your plugin
src/
plugin/ # Main thread code (runs in Figma sandbox)
main.ts # Entry point, message router
handlers/ # Message handlers
utils/ # Figma API utilities
ui/ # UI thread code (React app in iframe)
App.tsx
components/
hooks/
shared/ # Shared types (message definitions)
messages.ts # PluginMessage & UIMessage types
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 · 323 lines · 3,038 tokens per session scan A 5fb6bf4936aa
figma-plugin-core is a cursor rule published in the GitHub repository hoshikitsunoda/figma-plugins-vibe-coding-template (21 stars, last pushed 8mo ago), licensed MIT. It adds 3,038 tokens to every session, about $0.0152 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.