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/repository-builder)<a href="https://agentmods.dev/rules/jrpease/throughline/repository-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/repository-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/repository-builder"><img src="https://agentmods.dev/badge/rules/jrpease/throughline/repository-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.00136 | $0.02361 |
| Opus 5.5 | $0.00054 | $0.00944 |
| Sonnet 5.5 | $0.00027 | $0.00472 |
| Haiku 4.5 | $0.00014 | $0.00236 |
Grade A, and why
repository-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 3d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository builder
Turns the user's working folder into a scalable monorepo and advances their version-control stage. Defaults: pnpm + Turborepo, with a layout ready to grow into a full app:
my-design-system/
├── design-system.json (the manifest, already here)
├── package.json (workspace root)
├── pnpm-workspace.yaml
├── turbo.json
├── .gitignore
├── .env.example
├── packages/
│ ├── tokens/ (synced token output lands here — skill 6)
│ └── ui/ (components / Storybook live here — skill 7)
└── apps/ (empty, ready for a Next.js app later)
Calibrate first
Read user.codingLevel from the manifest and .throughline/references/coding-level.md.
Everything below describes the actions, which are identical for every user.
How much you explain each concept scales with the level — new gets plain-
language teaching of repos, env files, and secrets; comfortable gets terse
action statements. The hard secret-safety rules never scale.
The folder → local-git → github progression
Scope check first. If the user is bringing an existing app to retrofit or
migrate (not scaffolding a clean monorepo) — or the repo work is entangled with a
larger re-architecture — that has outgrown this skill. Follow
.throughline/references/scaling-up-handoff.md: surface risks and major parts, confirm scope,
and brainstorm/plan first. For a normal scaffold-from-scratch, continue here.
The user is at one of three workspace.stage values. This skill advances them
one step at a time, introducing each concept only when its payoff is concrete.
Read the current stage from the manifest and pick up where they are.
Stage A → scaffold the monorepo (still just a folder)
Create the workspace files (root package.json, pnpm-workspace.yaml,
turbo.json, packages/tokens, packages/ui, apps/, a sensible
.gitignore, and a .env.example). Record repo.packageManager = pnpm,
repo.monorepo = turborepo.
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.
- 3d ago Changed · -1 lines 801a92ff9769
- 1mo ago First seen · 182 lines · 136 tokens per session scan A 5a8174fe7f93
repository-builder is a cursor rule published in the GitHub repository jrpease/throughline (78 stars, last pushed 3d ago), licensed MIT. It adds 136 tokens to every session and 2,361 once invoked, about $0.0005 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.