rdocx: Command for Claude Code

.claude/commands/sync-sprint.md

sync-sprint is a command for Claude Code from tensorbee/rdocx. It costs 18 tokens per session (809 once invoked), scanned A, original, MIT.

A command for opening a new sprint, a planned development cycle, from the repository's sprint plan. It checks the previous sprint, creates or selects its Git branch, and generates the current sprint tracking file.

In plain words
What is it for?
Use it to start sprint SNN, create sprint/sNN from main, and populate the sprint's current-work document from the plan.
Why use it?
It prevents unfinished work from being silently left behind and gives the new sprint a consistent list of planned features and owners.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is tensorbee/rdocx's own configuration. It tells Claude Code how to work on rdocx itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rdocx configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/tensorbee/rdocx/main/.claude/commands/sync-sprint.md
Clone the repo
git clone --depth 1 https://github.com/tensorbee/rdocx

Made for: Claude Code.

Wrote 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.

agentmods badge for sync-sprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/tensorbee/rdocx/sync-sprint/github.svg)](https://agentmods.dev/commands/tensorbee/rdocx/sync-sprint)
Your own site
<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.

agentmods 80×15 button for sync-sprint

Your own site · 80×15
<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>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 26d ago against content hash 4c42859bb548, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/commands/sync-sprint.md · 90 lines

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

  1. Check the previous sprint is closed. Every F-ID in the outgoing CURRENT_SPRINT.md is done or explicitly carried. If any is still in-progress, stop and name it.

  2. Read the plan. Find #### Sprint SNN in docs/sprints/SPRINT_PLAN.md and 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.

  3. Create the branch. sprint/sNN off the latest main. Fetch first. If it exists already, check it out and say so rather than recreating it.

  4. Regenerate CURRENT_SPRINT.md using the template below. Every row starts pending with 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.

  5. Collect the spec references. For each F-ID, read its entry in docs/hld/14-development-backlog.md and the sections it cites, and list the distinct docs/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.

  6. 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.

  7. Initialise the run state. python3 scripts/sprint_workflow.py init SNN.

  8. Report the branch, the F-ID count and the estimated days. A validation-only sprint reports zero F-IDs and zero estimated implementation days.

Read the full file on GitHub · 90 lines

Changes

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.

  1. 26d ago First seen · 90 lines · 18 tokens per session scan A 4c42859bb548

Subscribe to this mod's changes

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.