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/mjmorales/claude-proveWrote 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/commands/mjmorales/claude-prove/scrum)<a href="https://agentmods.dev/commands/mjmorales/claude-prove/scrum"><img src="https://agentmods.dev/badge/commands/mjmorales/claude-prove/scrum.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.00016 | $0.00529 |
| Opus 5 | $0.00008 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
scrum 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 6d 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
Scrum
Agentic task management on the unified prove store. Tasks, milestones, tags, and run-links live in .prove/prove.db; CC-lifecycle hooks reconcile state at task boundaries (not commits).
The first token of $ARGUMENTS selects the route. No argument → print this routing table and exit.
Routing
| Arg | Action |
|---|---|
init |
Run claude-prove scrum init — one-shot importer for legacy planning/*. |
status |
Run claude-prove scrum status --human — compact text overview. |
next |
Run claude-prove scrum next-ready --human — ranked next tasks. |
alerts |
Run claude-prove scrum alerts --human — stalled WIP + orphan run report. |
task |
Delegate to scrum-master agent — interactive task lifecycle. |
milestone |
Delegate to scrum-master agent — milestone lifecycle. |
tag |
Delegate to scrum-master agent — tag taxonomy edits. |
link |
Delegate to scrum-master agent — link runs to tasks. |
init, status, next, alerts are direct CLI passthroughs — execute the bash command, surface output verbatim, exit. Pass any extra $ARGUMENTS tokens through (e.g., /scrum next --limit 5 → claude-prove scrum next-ready --human --limit 5; /scrum alerts --stalled-after-days 14 → claude-prove scrum alerts --human --stalled-after-days 14).
For task, milestone, tag, link: invoke the scrum-master agent with the full $ARGUMENTS string as task context. The agent owns interactive flows (AskUserQuestion gates, dep-graph reasoning, status-transition proposals).
Unrecognized argument
If $ARGUMENTS starts with anything outside the table, print the routing table above and stop. Do not guess.
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.
- 6d ago First seen · 34 lines · 16 tokens per session scan A 38b3bcd40fa0
scrum is a command published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 27d ago), licensed MIT. It adds 16 tokens to every session and 529 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.