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-status.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-status)<a href="https://agentmods.dev/commands/tensorbee/rdocx/sync-status"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sync-status/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-status"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/sync-status.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.00703 |
| Opus 5.5 | $0.00008 | $0.00281 |
| Sonnet 5.5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
sync-status 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-status [--fix]
Cross-check every place a fact is recorded twice. Reports drift by default.
--fix repairs only the mechanically derivable cases listed below.
Checks
-
Backlog against the HLD. Every F-ID in
docs/sprints/BACKLOG.mdexists indocs/hld/14-development-backlog.md, and the reverse. Sizes match. -
Backlog against the sprint plan. Every F-ID's
Sprintcolumn matches the sprint it appears under indocs/sprints/SPRINT_PLAN.md. -
Backlog against the current sprint. Every F-ID in
CURRENT_SPRINT.mdhas the same status inBACKLOG.md. This is the pair most likely to drift, because/complete-featurewrites both. -
AUTOGEN counts. Recompute every summary count from the rows. Mismatches are always a bug in a previous command, never a hand edit.
-
Design plans. Every
in-progressordoneF-ID has a plan. Every plan's status agrees with the backlog:approvedfor in-progress,completedfor done. -
AS_BUILT coverage. Every
doneF-ID has an entry. Every entry names a real F-ID. -
Review coverage. Every
doneF-ID has at least one.claude/reviews/F-XXX-*file whose final pass reports zero defects and zero smells. -
Dangling references. Every F-ID mentioned anywhere in
docs/or.claude/exists in the backlog. -
Spec references resolve. Every
docs/hld/path cited in a design plan or inCURRENT_SPRINT.mdexists. -
Dependencies are acyclic, and no
donestory depends on apendingone, which would mean it was completed out of order. -
Tracker arithmetic.
SPRINT_TRACKER.mdhas one row perdoneF-ID.
What --fix may repair
Only these, because only these are mechanically derivable:
- AUTOGEN summary counts (check 4).
- A
CURRENT_SPRINT.mdstatus that disagrees withBACKLOG.md, taking the backlog as authoritative (check 3). - The
Sprintcolumn inBACKLOG.md, takingSPRINT_PLAN.mdas authoritative (check 2).
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 · 73 lines · 19 tokens per session scan A 1e3713f89d7d
sync-status 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 703 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.