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-dev-modegit 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-dev-mode)<a href="https://agentmods.dev/rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-dev-mode"><img src="https://agentmods.dev/badge/rules/hoshikitsunoda/figma-plugins-vibe-coding-template/figma-dev-mode.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.1 | $0.00000 | $0.01253 |
| Opus 5 | $0.00000 | $0.00626 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
figma-dev-mode 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 6d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Dev Mode & Code Connect
Dev Mode provides developer-focused views and Code Connect links design to code.
Dev Mode Detection
// Check if plugin is running in Dev Mode
if (figma.mode === 'dev') {
console.log('Running in Dev Mode')
// Show developer-focused UI
} else {
console.log('Running in Design Mode')
}
Code Connect Overview
Code Connect links Figma components to their code implementations, showing relevant code snippets in Dev Mode.
Note: Code Connect is typically configured via a separate
figma.config.jsonfile and CLI, not through the Plugin API. See https://www.figma.com/developers/code-connect
Dev Mode Properties
Dev Resources
// Get dev resources attached to a node (async)
const resources = await node.getDevResourcesAsync()
for (const resource of resources) {
console.log(resource.name, resource.url)
}
// Add a dev resource (link to code, docs, etc.)
await node.addDevResourceAsync(
'https://github.com/org/repo/blob/main/src/Button.tsx',
'Component Source',
)
// Edit an existing dev resource
await node.editDevResourceAsync(
'https://github.com/org/repo/blob/main/src/Button.tsx',
{ name: 'Updated Name', url: 'https://new-url.com' },
)
// Delete a dev resource
await node.deleteDevResourceAsync(
'https://github.com/org/repo/blob/main/src/Button.tsx',
)
Annotations
// Dev Mode annotations are read-only in plugins
// They're managed through Figma's UI
Measurements & Specs
// Get node measurements
if ('absoluteBoundingBox' in node) {
const bounds = node.absoluteBoundingBox
console.log(`Position: ${bounds.x}, ${bounds.y}`)
console.log(`Size: ${bounds.width} x ${bounds.height}`)
}
// Get computed styles for dev handoff
function getNodeSpecs(node: SceneNode) {
const specs: Record<string, unknown> = {
name: node.name,
type: node.type,
}
if ('absoluteBoundingBox' in node) {
specs.bounds = node.absoluteBoundingBox
}
if ('fills' in node && Array.isArray(node.fills)) {
specs.fills = node.fills.filter((f) => f.visible !== false)
}
if ('effects' in node) {
specs.effects = node.effects.filter((e) => e.visible !== false)
}
if ('cornerRadius' in node) {
specs.cornerRadius = node.cornerRadius
}
if (node.type === 'TEXT') {
specs.fontSize = node.fontSize
specs.fontName = node.fontName
specs.lineHeight = node.lineHeight
specs.letterSpacing = node.letterSpacing
}
return specs
}
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.
- 6d ago First seen · 190 lines · 0 tokens per session scan A fe43e46713be
figma-dev-mode is a cursor rule published in the GitHub repository hoshikitsunoda/figma-plugins-vibe-coding-template (21 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,253 tokens. 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.