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/icon-system-builder)<a href="https://agentmods.dev/rules/jrpease/throughline/icon-system-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/icon-system-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/icon-system-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/icon-system-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.03987 |
| Opus 5.5 | $0.00038 | $0.01595 |
| Sonnet 5.5 | $0.00019 | $0.00797 |
| Haiku 4.5 | $0.00010 | $0.00399 |
Grade A, and why
icon-system-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 19d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Icon system builder
End state: a Figma page named Icons containing the relevant icon set as scalable, well-named components, ready to be consumed by components (skill 4) and swapped via instance properties.
Core principle: don't make Cursor draw 1,700 icons
The expensive, wrong path is Cursor generating icon components one by one, by hand, via the write mechanism — slow and token-hungry. Get to the end state via the cheapest mechanism that is also fully automated and produces clean, well-named components. "Cheapest" is not just Cursor tokens: a mechanism that burns near-zero tokens but makes the user hunt down a community file, duplicate it, and copy components by hand isn't actually cheap — it just moves the cost onto them. The library determines the mechanism, deterministically — same library, same path every run.
Lucide → fetch the official SVGs directly (default)
Default for Lucide: fetch the curated subset straight from the official source
repo and batch-componentize it. Lucide publishes every icon as a uniform 24px
SVG at a deterministic path (github.com/lucide-icons/lucide, icons/<name>.svg),
and the filename is the canonical name (arrow-right ↔ ArrowRight in
lucide-react). So the agent can do the whole thing hands-off:
- Resolve the subset to kebab-case icon names (see name validation below) and
pin a release tag — ideally the tag matching the installed
lucide-reactversion, so the Figma mirror and the code package are the same generation. - Batch-fetch each
https://raw.githubusercontent.com/lucide-icons/lucide/<tag>/icons/<name>.svg. A 404 means that icon doesn't exist at that version — report it and let the user pick a replacement. (This is the name-validation gate, for free.) - In one scripted pass, turn each SVG into a component via
figma.createNodeFromSvg(svg), convert to a component, name it per the naming contract (Step 3), and set the base size.
This is fully automated, official source-of-truth, deterministic-named, and
needs no manual user steps — strictly better than a community-file copy for a
library shaped like this. This is not the old "fetch SVGs off a website and
hand-prep them" anti-pattern: that meant a human manually downloading and cleaning
files. Batch-grabbing the official repo by deterministic path and scripting
createNodeFromSvg is cheap and hands-off.
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.
- 19d ago Changed · +4 lines 71d7c30333fc
- 1mo ago First seen · 281 lines · 96 tokens per session scan A 4c9266c9ca2e
icon-system-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 3,987 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ı.