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/jrpease/throughline/figma-environment-setupgit clone --depth 1 https://github.com/jrpease/throughlineWhat 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.00133 | $0.05467 |
| Opus 5 | $0.00067 | $0.02733 |
| Sonnet 5 | $0.00027 | $0.01093 |
| Haiku 4.5 | $0.00013 | $0.00547 |
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 2d 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 — 461 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 Figma skill does a cheap liveness check and, if it fails, points the user back here.
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"
"Here": Proceed to the existing manifest check below.
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.
- 2d 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 (76 stars, last pushed 4d ago), licensed MIT. It adds 133 tokens to every session and 5,467 once invoked, about $0.0007 per session on Opus 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
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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.