Borrowing it
Nothing to install: this file belongs to Osiris-DevWorks/smart-citizen. 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/Osiris-DevWorks/smart-citizen/main/.claude/commands/docs_sync_check.mdgit clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizenWrote 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/osiris-devworks/smart-citizen/docs_sync_check)<a href="https://agentmods.dev/commands/osiris-devworks/smart-citizen/docs_sync_check"><img src="https://agentmods.dev/badge/commands/osiris-devworks/smart-citizen/docs_sync_check/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/osiris-devworks/smart-citizen/docs_sync_check"><img src="https://agentmods.dev/badge/commands/osiris-devworks/smart-citizen/docs_sync_check.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.00804 |
| Opus 5.5 | $0.00008 | $0.00322 |
| Sonnet 5.5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
docs_sync_check 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 2mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docs_sync_check
Cross-check the running app's user-facing surface against the docs and tutorial. Catches drift introduced when a button is renamed in code but the doc still describes the old name, when a control is removed but the tutorial still points at it, or when a new feature ships without a docs update.
Severities
- Critical — a tutorial step in
src/gui/coach_mark.pyreferences a widget that no longer exists. Will crash or confuse first-time users. - Major — workflow steps in
docs/HELP.mdno longer match the code, or a user-facing string is described indocs/HELP.md/docs/ABOUT.mdunder a name that no longer exists in code. - Minor — a feature mentioned in
docs/ABOUT.mdorREADME.mdhas been removed/renamed but isn't user-facing-critical (e.g. a string label drift that still reads naturally).
Inputs
src/gui/*.py— user-facing strings (window titles, button/menu/tab labels, dialog text, log lines users see in the Log Tab).docs/HELP.md— step-by-step user instructions.docs/ABOUT.md— feature summary.src/gui/coach_mark.py—CoachMarkStepentries that drive the guided tour.README.md— Features section and Screenshots labels.
Checks
- Tutorial widget validity (Critical): every
CoachMarkStepincoach_mark.pyreferences a target widget — confirm the widget still exists (grep for its attribute name onMainWindowand the relevant tabs). Flag any step whose target was deleted or renamed. - String drift in HELP/ABOUT (Major): pull every user-facing literal from
src/gui/and check whether any noun phrase used inHELP.mdorABOUT.mdis no longer present in the code (likely renamed). Flag with the doc file:line plus the suspected new wording from the code. - Workflow currency (Major):
HELP.mddescribes Apply / Restore / Extract / Reset user.ini / Export Loc-Pack / channel switch. If a recent diff changed any of these flows, surface the matching section ofHELP.mdfor review. - Feature parity (Minor, escalate to Major if HELP.md has a how-to step for the affected feature):
HELP.md,ABOUT.md, and README's Features list should match the code. Flag features described in docs that no longer exist, and code features that aren't surfaced in any of the three.
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.
- 2mo ago First seen · 52 lines · 19 tokens per session scan A edc0eeaa50d2
docs_sync_check is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (114 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 804 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.