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/token-sheet-builder)<a href="https://agentmods.dev/rules/jrpease/throughline/token-sheet-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/token-sheet-builder/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/token-sheet-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/token-sheet-builder.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.00096 | $0.02553 |
| Opus 5.5 | $0.00038 | $0.01021 |
| Sonnet 5.5 | $0.00019 | $0.00511 |
| Haiku 4.5 | $0.00010 | $0.00255 |
Grade A, and why
token-sheet-builder 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 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.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token sheet builder
Creates a polished visual reference of the design system's tokens and styles on a dedicated Figma page called Foundations. This is the artifact designers and stakeholders actually look at — so it must be beautiful and on-brand, not a utilitarian dump of swatches.
Live vs regenerated — set expectations clearly
Bind to variables wherever Figma allows so the sheet live-updates for those
properties: a color swatch bound to gray/50 (in _Color/Primitive) re-colors
automatically when that primitive changes; spacing/radius examples bound to the variables resize
automatically. But labels, hex/value text, token names, descriptions, and the
set of tokens shown (adding/removing tokens) are snapshots — they don't
auto-update. So tell the user plainly: "The swatches update live when you change
a value, but if you rename tokens, change descriptions, or add/remove tokens,
re-run this skill to refresh the page." The sheet is regenerable; re-running
refreshes the snapshot parts.
(Tie-in: when the sync skill runs after token changes, refreshing Foundations is a sensible companion step — the sheet and the synced code both reflect Figma.)
Prerequisites
Needs tokens in Figma (tokens.semanticBuilt true) and a live Figma connection.
If tokens don't exist, offer to run token-builder. If Figma isn't connected,
offer figma-environment-setup. The plugin writes to Figma through Console MCP. If figma.mechanism holds anything other than console-mcp, say that value is no longer supported and offer figma-environment-setup to reset it.
Before scripting any figma_execute, read
.throughline/references/figma-scripting.md. This sheet builds large
swatch/type grids — exactly the layouts that hit the two worst traps: the
resize() axis-lock (collapses a color grid or type-meta column to ~10px) and the
single-call layoutWrap = "WRAP" timeout on big grids (build manual rows or split
across calls instead). Also run the single-bridge-instance preflight before writing.
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 dae7733b1e48
- 19d ago Changed · +4 lines 14ba8a0861fe
- 1mo ago First seen · 181 lines · 96 tokens per session scan A b6aed46d4bb3
token-sheet-builder is a cursor rule published in the GitHub repository jrpease/throughline (78 stars, last pushed 3d ago), licensed MIT. It adds 96 tokens to every session and 2,553 once invoked, about $0.0004 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-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ı.