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/close-sprint.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/close-sprint)<a href="https://agentmods.dev/commands/tensorbee/rdocx/close-sprint"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/close-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/tensorbee/rdocx/close-sprint"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/close-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.00019 | $0.01575 |
| Opus 5.5 | $0.00008 | $0.00630 |
| Sonnet 5.5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
close-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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/close-sprint SNN [--next SMM]
Merge the sprint branch to main, tag it, push both, and open the next sprint.
A prepared release follows through /release at this exact main merge SHA.
This is the only command in the repository that may touch main or create an
sNN sprint tag. /release alone owns v* release tags and crates.io
publication.
Steps
-
Pre-flight.
python3 scripts/sprint_workflow.py close-preflight SNN, plus:- Every F-ID in
CURRENT_SPRINT.mdisdone, or explicitly carried with a stated reason. - The working tree is clean.
- The current branch is
sprint/sNN. mainhas no commits the sprint branch lacks. If it does, rebase or mergemainin first and re-verify.- No worker work is stranded.
git worktree listandgit branch --list 'work/*'against the run state.close-preflightalready refuses an unconsumed.claude/handoffs/F-XXX-ready.md. Record the completed workers that become cleanup targets after the push. A carried worker, an untracked branch or a worktree absent from the run state is not a cleanup target.
- Every F-ID in
-
Consume final verification. Require the latest applicable passing full sprint evidence and any validated completion-only metadata adoption. Run missing or invalidated categories only, never the full gate a second time because
/close-sprintwas invoked. Completion metadata requires applicable post-edit policy checks as well as prose. A clean code tree cannot excuse capability rows still owned by done stories. Failed or missing evidence blocks close. -
Consume
/sprint-review SNN. Require its latest clean bounded review. Invoke it only when absent or invalidated by material changes. Do not run a confirmation pass after clean review. Source remediation requires affected checks and review of its new material, not automatic repetition of all work. -
Confirm the milestone gate if this sprint closes one. Find the "End-of-milestone gate" in
docs/hld/14-development-backlog.mdand check it explicitly. Some gates are manual, such as opening corpus decks in PowerPoint. Do not mark a manual gate as met without performing it.
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 · +3 lines 38d92a5bb978
- 11d ago Changed · +7 lines be21b50ab503
- 26d ago First seen · 121 lines · 19 tokens per session scan A d2221d5a6b22
close-sprint is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,575 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
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.