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/azrtydxb/procoderWrote 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/azrtydxb/procoder/sprint)<a href="https://agentmods.dev/commands/azrtydxb/procoder/sprint"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/sprint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/azrtydxb/procoder/sprint"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/sprint.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00427 |
| Opus 5.5 | $0.00010 | $0.00171 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
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 1mo 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
The user invoked /procoder:sprint with arguments: $ARGUMENTS
The command below is the procoder binary on PATH.
A sprint is a commitment, not a calendar: a goal plus the stories pulled into it, opened and closed explicitly. One sprint is active at a time — that is the WIP limit, and the point.
procoder sprint open <goal>— refuses while a sprint is active; otherwise prints the sprint file for you to write. State a real goal: what this sprint delivers, not a date range.procoder sprint pull <story-id>...— commit stories to the active sprint. Done, missing, or already-committed stories are refused individually; the rest still pull.procoder sprint status— goal, committed stories with statuses, done/total and carried counts. Run it before claiming progress.procoder sprint carry <story-id> <reason>— return an unfinished story to the backlog, with the reason recorded in the story file. Lean makes unfinished work visible; carrying without a reason is refused.procoder sprint close— REFUSES while a committed story is neither done nor carried. Finish it (backlog close story <id>) or carry it with a reason, then close; the sprint file gets a Result section with committed/done/carried counts and a Retro scaffold.- Fill the Retro before moving on — what slowed us, what we change,
one adaptation worth keeping. The retro is the price of the next
sprint:
sprint openrefuses while the last one's Retro is empty ([sprint] retro = "off"opts a repo out).
With arguments, run the matching subcommand and act on its output.
Without arguments, run status and report where the sprint stands.
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.
- 1mo ago First seen · 36 lines · 26 tokens per session scan A 3bbac814e711
sprint is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 427 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
logic-diff
Check two code versions for semantic equivalence — use after a refactor or rewrite.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
plan-backlog
Turn an idea, brief, or document into a well-formed backlog and create it in your tracker after approval. Guided by default; --quick for a one-shot draft. Usage - /plan-backlog [--quick].
plan-definition
Turn a spark (an idea, even a one-liner) into a clear product definition through a guided discovery phase, then hand it to plan-backlog. Facilitate, never decide. Usage - /plan-definition.
team-review
Coordinate a multi-role review of the current change.