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 commands/pactkit/claude-code-plugin/project-sprintgit clone --depth 1 https://github.com/pactkit/claude-code-pluginWhat 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.00010 | $0.00444 |
| Opus 5 | $0.00005 | $0.00222 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
project-sprint 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 33 lines · 10 tokens per session scan A 14b75a9e60da
project-sprint is a command published in the GitHub repository pactkit/claude-code-plugin (5 stars, last pushed 2d ago), with no licence file. It adds 10 tokens to every session and 444 once invoked, about $0.0001 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 commands, from other repositories
codebase-audit
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
status
Pipeline status for a spec/feature — or, with no slug, the whole-project delivery report (every spec/backlog/quick-task + GitHub/Linear cross-ref).
dashboard
Launch the local planr dashboard — a live, read-only view of the .planr/ graph (Overview · Graph · Board · List · Sprints · Activity). Reuses a running server if one already owns the port.
sync
Reconcile spec ↔ quick-task ↔ issue-tracker alignment across .planr/ — guarantee every shippable spec carries its externalization Quick Task (the unit pushed to Linear/GitHub for PO + manager visibility), fix deterministic drift, surface judgment calls. Read-only by default.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.