Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/KirKruglov/claude-project-managerWrote 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/kirkruglov/claude-project-manager/sync-check)<a href="https://agentmods.dev/commands/kirkruglov/claude-project-manager/sync-check"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/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/kirkruglov/claude-project-manager/sync-check"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/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.00013 | $0.00418 |
| Opus 5.5 | $0.00005 | $0.00167 |
| Sonnet 5.5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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.
What it actually says
Sync Check Command
Purpose
Review cross-stream dependencies and synchronization status in Phase 5. Identify cross-workstream blockers, dependency conflicts, and synchronization issues between dev, marketing, and ops streams.
Steps
-
Verify phase 5 status
- Read
project-state.md - Check
phasefield - If not phase 5:
- Inform user: "Sync check is only available in Phase 5 (execution wind-down)"
- Do not proceed
- If phase 5, continue
- Read
-
Query cross-stream tasks
- Query ~~project tracker for all active tasks across workstreams:
- Development (dev)
- Marketing (marketing)
- Operations (ops)
- Retrieve task status, dependencies, and assigned executors
- Identify tasks with cross-stream dependencies
- Query ~~project tracker for all active tasks across workstreams:
-
Analyze synchronization
- Map task dependencies across streams
- Identify critical path items requiring cross-stream coordination
- Detect blocked tasks awaiting completion from other streams
- Note tasks on track vs at-risk
-
Generate sync report
- Trigger
monitor-progressskill withreport_type=sync - Include:
- Cross-stream dependency matrix
- Blocker identification and impact
- At-risk items requiring escalation
- Recommended actions to unblock
- Trigger
-
Save report
- Save report to
reports/sync-report-{YYYY-MM-DD}.md - Include timestamp and phase confirmation
- Save report to
-
Highlight critical blockers
- Extract high-impact cross-stream blockers
- For each blocker:
- Show affected workstreams
- Show impact (tasks/timeline affected)
- Show recommended resolution path
-
Update project state
- Update
project-state.mdwith:- Last sync check timestamp
- Number of active cross-stream blockers
- Critical path status
- Log action in project audit trail
- Update
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 First seen · 59 lines · 13 tokens per session scan A fe7200623791
sync-check is a command published in the GitHub repository KirKruglov/claude-project-manager (7 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 418 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-31.
Other commands, from other repositories
progress-report
Create weekly or monthly progress reports with milestone tracking, budget status, and risk assessments.
project-estimate
Generate detailed project cost estimates with line items, labor, materials, contingency, and summary breakdowns.
meeting-followup
Transform meeting notes into structured summaries, action items, and professional follow-up emails.
change-order
Draft change order documentation with scope changes, cost impacts, schedule adjustments, and approval routing.
project-proposal
Generate design proposals with scope of work, concept overview, phasing, fee structure, and terms.
spec-sheet
Draft FF&E schedules and material specifications with manufacturer details, dimensions, and lead times.