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 skills/jtsternberg/claude-plugins/compounding-preflightnpx skills add jtsternberg/claude-plugins --skill compounding-preflightgit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWrote 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/jtsternberg/claude-plugins/compounding-preflight)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/compounding-preflight"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/compounding-preflight.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 | $0.00078 | $0.00635 |
| Opus 5 | $0.00039 | $0.00318 |
| Sonnet 5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
compounding-preflight 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 yesterday.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compounding Preflight
Diff-check a change-set against the ledger at docs/compounding.md,
both directions: does the change violate an entry, and does it teach one?
Steps
-
Resolve the change-set. Default
git diff main...HEAD(or the staged/working diff if no branch delta); a PR number or explicit range wins when given. -
Read
docs/compounding.mdin full — the bold headlines are the rules; the Known False Positives section is the list of things to NOT report. -
Scan the diff against each headline. For docs/skills rules, include changed
*.mdfiles AND script headers/--helptext. Cheap greps first (the phrases and patterns entries name), judgment second. -
Report violations as
rule headline → file:line → one-line fix, most severe first. Anything matching a Known False Positive is not a finding. -
Tripwire scan. Parked beads declare where their knowledge bites via a
tripwire-paths:line. Run the shared matcher — the same engine the distributedbeads-workflow:tripwire-scanskill and its PostToolUse hook use — against the change-set:bash plugins/beads-workflow/scripts/tripwire-match.sh scanReport each hit (
bead id → matched file → the bead's one-line why) so the author acts on it, consciously defers, or closes the bead as satisfied. Pass a range/commit to scan a specific delta; add--jsonfor machine output. The matcher handles anchor precision (comment / string / git-ref-pinned range) and self-trip suppression (in_progress beads self-suppress) — no hand-grepping. -
Propose compounding. If the change-set fixed a bug class, absorbed a review correction, or removed accreted text, draft the entry (headline + ≤3 sentences + provenance) and ask whether to add it — the write gate at the top of the doc decides format; a one-time incident does not qualify.
-
Prune check. Name any existing entry this change-set made obsolete or turned into a mechanical guard (then the entry's catch text becomes a pointer to the guard, or the entry is deleted).
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.
- yesterday Changed · +8 lines cda279778fe5
- 5d ago First seen · 37 lines · 78 tokens per session scan A f63cc0aeea03
compounding-preflight is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 635 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…