Borrowing it
Nothing to install: this file belongs to tensorbee/rdocx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tensorbee/rdocx/main/.claude/commands/sprint-review.mdgit clone --depth 1 https://github.com/tensorbee/rdocxWrote 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/tensorbee/rdocx/sprint-review)<a href="https://agentmods.dev/commands/tensorbee/rdocx/sprint-review"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sprint-review/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/tensorbee/rdocx/sprint-review"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sprint-review.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.00018 | $0.01004 |
| Opus 5.5 | $0.00007 | $0.00402 |
| Sonnet 5.5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
sprint-review 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sprint-review SNN [--pass N]
Review the sprint's integrated diff, which is not the same as the sum of its
feature reviews. /microscope sees one F-ID. This sees what they did to each
other.
This command changes no code. Fixes are normal F-IDs or amendments made by the implementing session between passes.
Steps
-
Establish the diff.
sprint/sNNagainst the merge base withmain. Report the file count, line count and the crates touched. -
Read the sprint contract.
docs/sprints/CURRENT_SPRINT.md, its goal, its definition of done, and the milestone gate fromdocs/hld/14-development-backlog.md. -
Review the integrated delta. Record the actual implementer and reviewer. Honor any requested reviewer in run state, without impersonating another model. Inspect consumer maps, A-ID evidence and discriminating fixture inputs. Challenge cross-story policy agreement and final completion state, not only isolated code. Check actual rendered outputs for rendering criteria, empty cases combined with compatibility/scoping modes, and before/after mutation state. Compare the reviewed final metadata with policy-test inputs.
Challenge lifecycle-wide placement invariants, promised binding methods and raw-XML validation, even when creation and round-trip tests pass. Distinguish a failed intermediate build from a later identified successful artifact. Read the semantic outcome of performance/render reports, not only their process exit. Keep source-bound timing, structural work bounds and native qualification separate. A passing ratio cannot discharge another blocker.
Consume the actual final full and oracle observations. This command does not rerun them. Completion/review-only changes require bounded metadata adoption, not another product gate.
Review the aspects that only appear at sprint scope:
Aspect Looks for interactionTwo F-IDs that are individually correct and jointly wrong duplicationThe same helper written twice in one sprint under different names layeringAn oxml-*crate that gained a dependency onrdocx-*orrpptx-*harnessEvery hash-harness delta declared, justified and consistent with its AS_BUILT entry gateDoes the milestone gate actually hold, tested rather than asserted docsHLD sections the sprint contradicted but did not update depsNew dependencies, each with a named consumer surfacePublic API added that no story called for
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 Changed · +16 lines 4526c4ed6738
- 11d ago Changed · +4 lines 394816b54292
- 26d ago First seen · 92 lines · 18 tokens per session scan A 3c50092946f6
sprint-review is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,004 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-10-04.
Other commands, from other repositories
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
anchors
List what each requirement tag anchors to (read-only).
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
luda
Invoke Luda, your Scrum Master, for board integrity — orphan work items, plan-vs-tracker divergence, Done-without-negative-criteria, parked-without-a-trigger — plus ticket creation and team orchestration.