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/component-pipelinegit 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.00119 | $0.01018 |
| Opus 5 | $0.00060 | $0.00509 |
| Sonnet 5 | $0.00024 | $0.00204 |
| Haiku 4.5 | $0.00012 | $0.00102 |
Grade A, and why
component-pipeline 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 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.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component pipeline (orchestrator)
Sequences a single new component through the whole flow: Figma → tokens → code/stories. This skill holds zero domain logic of its own — it is a sequencer that invokes the real skills and gates each stage on a human confirmation. All the actual work lives in the skills it calls; this keeps it from rotting when those skills improve.
When to use vs. the individual skills
Use this for one new component, end to end, on a system that already has foundations (tokens, repo, sync, Storybook). For initial setup, the individual skills run directly. This is the "I have a system; add a Tooltip and take it all the way to a tested story" flow.
Prerequisites
Read the manifest. The pipeline assumes foundations exist: tokens built, a repo
at least local-git, sync configured, Storybook initialized. For any missing
piece, offer to run the relevant skill — but note that if a lot is missing, the
user probably wants the individual setup skills first, not this orchestrator.
The sequence (confirm between every stage)
Confirm the goal first: "New Tooltip component, right? I'll build it in Figma,
sync any new tokens, then build the code component and its stories — checking
with you between each step." Then:
Stage 1 — Build in Figma (invoke component-builder)
Invoke the component-builder rule for this one component: brainstorm its
variant matrix and slots, build it bound to tokens following the component
standards, capture its slot contract. Checkpoint: show the finished Figma
component. Get explicit confirmation before continuing.
If the build fails or the user wants changes, stop here — they still have a valid (or fixable) Figma component and a clean place to resume. Never push a half-built component down the pipeline.
Stage 2 — Sync new tokens (offer token-sync-layer)
The new component may have introduced new tokens (a new semantic role, a new
spacing step). Offer: "This component added a couple of new tokens — want me to
sync them to code now?" If yes, invoke token-sync-layer (which lands a
reviewable PR per its own rules). If the component introduced no new tokens, say
so and skip. Checkpoint: confirm the sync PR before continuing.
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 · 86 lines · 119 tokens per session scan A 1bcb00897c10
component-pipeline is a cursor rule published in the GitHub repository jrpease/throughline (76 stars, last pushed 4d ago), licensed MIT. It adds 119 tokens to every session and 1,018 once invoked, about $0.0006 per session on Opus 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
general
Wonder Blocks design system conventions, component patterns, and coding standards.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-designer
UI designer rules — theme variables, color usage, no literal hex in app code.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.