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/sprint-report)<a href="https://agentmods.dev/commands/kirkruglov/claude-project-manager/sprint-report"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/sprint-report/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/sprint-report"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/sprint-report.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.00005 | $0.01006 |
| Opus 5.5 | $0.00002 | $0.00402 |
| Sonnet 5.5 | $0.00001 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
sprint-report 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Report
Generate a comprehensive weekly progress report for the current sprint. Available only in Phase 3 (Execution) and beyond.
Input
- sprint-number (optional): Sprint number. If omitted, calculate from project start date and current week.
Process
1. Validate Project Phase
Read project-state.md:
- Verify current phase is 3, 4, or 5 (Execution, Monitoring, or Closure)
- If phase < 3, display error: "Sprint reports are only available during Execution phase (3) and beyond"
- Continue only if phase >= 3
2. Determine Sprint Number
If sprint-number not provided in argument:
- Calculate from project_state.md
phase_start_dateor project initiation date - Use ISO week numbering: sprint 1 = week 1, sprint 2 = week 2, etc.
- Display calculated sprint number to user
If sprint-number provided:
- Validate it's a positive integer
- Use provided value
3. Read Project Plan
Read 02-planning/project-plan.md to get:
- Planned milestones for this sprint
- Planned work items and deliverables
- Sprint duration and dates
- Success criteria
4. Read Current Project State
Read project-state.md to get:
- Artifacts completed this sprint
- Artifacts in progress this sprint
- Artifacts blocked or at risk
- Current phase status
5. Query Project Tracker (~~project tracker)
Contact external project tracker (if integrated) to pull:
- Current sprint tasks and their status
- Burndown rate and velocity
- Blockers and risks reported
- Team capacity and utilization
If no external tracker:
- Log note: "Project tracker integration not available - using project-state.md only"
6. Trigger Monitor Progress Skill
Call skill #18 (monitor-progress) with parameters:
artifact_id: "18"
report_type: "progress"
sprint_number: [calculated or provided]
project_path: "."
Skill will produce comprehensive analysis including:
- Actual vs. planned progress
- Schedule variance
- Budget variance (if available)
- Risk trajectory
- Next week forecast
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 · 169 lines · 5 tokens per session scan A 26a9fa749f01
sprint-report is a command published in the GitHub repository KirKruglov/claude-project-manager (7 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 1,006 once invoked, about $0.0000 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
project-estimate
Generate detailed project cost estimates with line items, labor, materials, contingency, and summary breakdowns.
change-order
Draft change order documentation with scope changes, cost impacts, schedule adjustments, and approval routing.
progress-report
Create weekly or monthly progress reports with milestone tracking, budget status, and risk assessments.
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.
meeting-followup
Transform meeting notes into structured summaries, action items, and professional follow-up emails.