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/sync-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/sync-sprint)<a href="https://agentmods.dev/commands/tensorbee/rdocx/sync-sprint"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sync-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/sync-sprint"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sync-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.00018 | $0.00809 |
| Opus 5.5 | $0.00007 | $0.00324 |
| Sonnet 5.5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
sync-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 26d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-sprint SNN
Open sprint SNN. Regenerates docs/sprints/CURRENT_SPRINT.md from
SPRINT_PLAN.md and creates the sprint branch.
Steps
-
Check the previous sprint is closed. Every F-ID in the outgoing
CURRENT_SPRINT.mdisdoneor explicitly carried. If any is stillin-progress, stop and name it. -
Read the plan. Find
#### Sprint SNNindocs/sprints/SPRINT_PLAN.mdand take its goal and F-ID table. If the sprint is not there, stop. A sprint may omit the F-ID table only when its plan explicitly defines it as a validation-only boundary. -
Create the branch.
sprint/sNNoff the latestmain. Fetch first. If it exists already, check it out and say so rather than recreating it. -
Regenerate
CURRENT_SPRINT.mdusing the template below. Every row startspendingwith owner-. For a plan-defined validation-only boundary, add**Validation-only**: yes, retain the empty wave table, and state that the sprint has no implementation F-IDs. Never infer validation-only status from a missing or malformed table. -
Collect the spec references. For each F-ID, read its entry in
docs/hld/14-development-backlog.mdand the sections it cites, and list the distinctdocs/hld/documents with one line on what each contributes. For a validation-only sprint, collect the documents that define the boundary and its gates. This section is what makes the sprint file useful rather than a duplicate of the plan. -
Write the sequencing note. Order the rows by dependency, not by F-ID, and explain any ordering a reader would not predict. For a validation-only sprint, state that there is no implementation order and name the next work the boundary protects.
-
Initialise the run state.
python3 scripts/sprint_workflow.py init SNN. -
Report the branch, the F-ID count and the estimated days. A validation-only sprint reports zero F-IDs and zero estimated implementation days.
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.
- 26d ago First seen · 90 lines · 18 tokens per session scan A 4c42859bb548
sync-sprint 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 809 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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.