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.
/plugin marketplace add cahenesy/throughlinenpx agentmods add plugins/cahenesy/throughline/marketplacegit clone --depth 1 https://github.com/cahenesy/throughlineGrade A, and why
throughline 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.
What it actually says
{
"name": "throughline",
"description": "Throughline development kit: a PRD/TDD/ADR design-doc pipeline with phase-gate PRs, an independent design-critique gate, toolchain bootstrap, and gated unattended implementation (failing-test-first + mechanical verify + independent review on a diverse model before any TDD is marked done; one PR per TDD).",
"owner": { "name": "Chris Henesy" },
"plugins": [
{
"name": "throughline",
"source": "./",
"description": "Throughline bootstrap kit: project-setup skill, standard subagents (incl. an independent design-reviewer), gated test-first/verify implementation, and a format+lint hook. Superpowers and pr-review-toolkit are optional delegates."
}
]
}
What ships with it
2 files beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 13 lines scan A e7208c6d22ed
throughline is a plugin published in the GitHub repository cahenesy/throughline (2 stars, last pushed 16d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
dx
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
rvdbreemen-adr-kit
Marketplace hosting the adr-kit plugin: a drop-in Architecture Decision Record toolkit for AI coding agents.
superpipelines-marketplace
Marketplace for the superpipelines plugin: design and run multi-agent AI pipelines.
forwward-teams
(forwward) Lean agent skills for building, shipping, strategy, and growth — no context bloat.