Borrowing it
Nothing to install: this file belongs to Washingtonwei/project-pulse. 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/Washingtonwei/project-pulse/main/.claude/commands/sync-check.mdgit clone --depth 1 https://github.com/Washingtonwei/project-pulseWrote 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/washingtonwei/project-pulse/sync-check)<a href="https://agentmods.dev/commands/washingtonwei/project-pulse/sync-check"><img src="https://agentmods.dev/badge/commands/washingtonwei/project-pulse/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/washingtonwei/project-pulse/sync-check"><img src="https://agentmods.dev/badge/commands/washingtonwei/project-pulse/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.00000 | $0.03204 |
| Opus 5.5 | $0.00000 | $0.01282 |
| Sonnet 5.5 | $0.00000 | $0.00641 |
| Haiku 4.5 | $0.00000 | $0.00320 |
Grade A, and why
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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-check — Spec ↔ Code conformance audit
Detect drift between the requirements docs and the actual codebase — where built code diverges from the spec, where the spec is unimplemented, and where code exists that no spec describes. This is the periodic companion to /spec-build.
/spec-build vs /sync-check — two different jobs, don't conflate them:
/spec-build= do the docs agree with each other? Intra-doc consistency (anchors, slugs, FR/BR refs, UC↔traceability). Mechanical, deterministic, cheap, auto-fixes. Run it freely after doc edits./sync-check(this) = do the docs agree with the code? Spec↔code conformance. Mostly semantic (read code, judge whether a rule is enforced), expensive, somewhat non-deterministic, and report-mostly — every finding needs a human fix-code-vs-amend-doc decision, so it never edits code and never "auto-fixes" a divergence. Its only write is appending draftOI-nitems todocs/requirements/OPEN-ISSUES.md. If a finding is an unfixed security defect, theOI-nitem there stays terse and the reproduction detail goes in the untrackedSECURITY-BACKLOG.mdat the repo root instead — the repo is public (seedocs/CLAUDE.md).
Run /spec-build first (or assume it passes) — /sync-check relies on the docs being internally consistent and the traceability matrix being current. This command reuses, does not duplicate, /spec-build's UC↔traceability coverage check.
Arguments / scope
/sync-check [scope] where scope is one of:
- (none) → changed-since-last-run (default). Read the last-audit baseline marker in
OPEN-ISSUES.md(see Phase 0),git diff <baseline>..HEAD --statto find changedbackend//frontend//docs/paths, and scope the semantic Phase B to the BRs/UCs/areas those touch. Phase A (mechanical) always runs in full — it's cheap. --full→ exhaustive: every BR, every UC main-flow + extensions, every endpoint and enum. Expensive; this is the deliberate 4-pass audit. Use after large changes or on a schedule.<area>(e.g.EVA,DOC,ram/document,BR-deletion-integrity) → scope to one UC-area, package, or a set of BRs.
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.
- 1mo ago Changed d9ada285a056
- 2mo ago First seen · 94 lines · 0 tokens per session scan A 7fdabb73fddc
sync-check is a command published in the GitHub repository Washingtonwei/project-pulse (2 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,204 tokens. 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-31.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).