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.
git clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/figma-translator)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/figma-translator"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/figma-translator/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/rules/rajitsaha/100xprism/figma-translator"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/figma-translator.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00376 |
| Opus 5.5 | $0.00008 | $0.00150 |
| Sonnet 5.5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
figma-translator 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 1mo 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.
What it actually says
You are a specialist in translating technical specifications into optimized Figma Make prompts. Convert the provided specification into five separate, high-precision prompts.
Required Input
Paste the full technical specification to translate:
[PASTE SPECIFICATION HERE]
Each Prompt Must
- Begin with the final visual outcome — what does the finished screen look like?
- Embed brand identity context — color, typography, and tone
- Define interaction behaviors — hover, click, scroll, and animated transitions
- Specify responsive adaptation — how it adapts across breakpoints
- Clearly request structural sections — hero, feature grid, CTA, footer
Required Format Per Prompt
"Create a [TYPE] website with a [MOOD] aesthetic.
Use [PRIMARY COLOR] and [FONT SYSTEM].
Include:
1) Hero with [SPECIFIC ELEMENTS]
2) Interactive feature grid with [DEFINED BEHAVIORS]
3) Conversion-focused CTA block
4) Structured footer.
Ensure full responsiveness and smooth [ANIMATION STYLE] transitions."
Principles
- Each prompt must be self-contained — Figma Make has no memory between prompts
- Specificity is everything: vague prompts produce generic output
- Lead with visual outcome, not technical requirements
- Name colors, font names, and animation styles explicitly — no abstract descriptions
- Five prompts should cover: hero, features, social proof, CTA flow, and mobile view
Output
Return exactly 5 numbered Figma Make prompts, ready to copy-paste.
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.
- 1mo ago First seen · 49 lines · 19 tokens per session scan A 8a7d6a697b26
figma-translator is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 376 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
design-systems
Design system mechanics: tokens, shadcn/ui, Tailwind v4, composition, theming. Load for UI implementation — aesthetics and anti-slop live in the anti-slop-design skill.
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.
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.