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 skills add jrpease/throughline --skill repository-buildergit 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/skills/jrpease/throughline/repository-builder)<a href="https://agentmods.dev/skills/jrpease/throughline/repository-builder"><img src="https://agentmods.dev/badge/skills/jrpease/throughline/repository-builder.svg" alt="Measured on agentmods" 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.00000 | $0.02233 |
| Opus 5 | $0.00000 | $0.01117 |
| Sonnet 5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00223 |
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 7d 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 — 178 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 (handing off to Superpowers if available, else planning
natively — never required). 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.
- 7d ago First seen · 178 lines · 0 tokens per session scan A a000e0dd8d69
repository-builder is a skill published in the GitHub repository jrpease/throughline (76 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,233 tokens. 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".