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/jrpease/throughlineWrote 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/jrpease/throughline/figma-environment-setup)<a href="https://agentmods.dev/rules/jrpease/throughline/figma-environment-setup"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/figma-environment-setup/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/jrpease/throughline/figma-environment-setup"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/figma-environment-setup.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.00133 | $0.05591 |
| Opus 5.5 | $0.00053 | $0.02236 |
| Sonnet 5.5 | $0.00027 | $0.01118 |
| Haiku 4.5 | $0.00013 | $0.00559 |
Grade B, and why
figma-environment-setup scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo chown -R $(whoami) ~/.npm How it starts
The opening of the file, as written. The whole thing — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma environment setup
This skill does three foundational jobs, in order:
- Discover where you're working — find or create the project directory, scan what's already there, and set expectations.
- Create the local working folder and write the
design-system.jsonmanifest into it (if not already present from step 1). - Connect Cursor to Figma so later skills can read and write the file, then verify the connection works.
It is the required first step. Every other skill that calls Figma itself does a
cheap liveness check and, if it fails, points the user back here. (The orchestrators
component-pipeline and retrofit-planner call Figma only through the skills they
invoke, and token-crosswalk-builder works from the manifest and token files.)
Who you're talking to
Assume the user is design-fluent but may have never set up a developer tool, created an API token, or used a terminal before. Explain every concept the first time it appears, in one plain sentence. Never assume they know what a "token", "MCP server", "config file", or "package manager" is. Be warm and concrete. When you ask them to do something outside the chat (in Figma, on a website), give the exact click path, not a vague instruction.
Read .throughline/references/manifest-schema.md before writing the manifest so you use the
correct field names and defaults.
Step 0 — Intake (Locate → Scan → Brief)
This step runs before everything else. Establish where you're working, read what's already there, and set the user's expectations before taking any action. It has three phases in sequence.
Phase 1: Locate
Open by surfacing the user's current working directory and presenting three explicit options — no assumptions made about where they want to work or whether they have started anything already:
"Before we get started, I want to make sure we're working in the right place. You're currently in:
[current working directory path]Where should we set up?
- Here — this directory is where the design system should live
- Somewhere else — I have a project at a different path
- A new folder — create a fresh folder somewhere"
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 Changed · -2 lines 3e8355e55b30
- 16d ago Changed · +9 lines 10df139d4c77
- 1mo ago First seen · 461 lines · 133 tokens per session scan B 380d4d13ed2d
figma-environment-setup is a cursor rule published in the GitHub repository jrpease/throughline (78 stars, last pushed 3d ago), licensed MIT. It adds 133 tokens to every session and 5,591 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.