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.
npx agentmods add commands/kirkruglov/claude-project-manager/statusgit 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/status)<a href="https://agentmods.dev/commands/kirkruglov/claude-project-manager/status"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/status.svg" alt="Measured on agentmods" 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.00008 | $0.00634 |
| Opus 5 | $0.00004 | $0.00317 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
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 6d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status
Display comprehensive current state of the project including phase, artifacts, recent activity, and recommended next actions.
Process
1. Read Project State
Read project-state.md to extract:
- Current phase
- Count artifacts by status (not started, in progress, approved, completed)
- Last update timestamp
2. Read Recent Logs
Read the last 10 entries from logs/log.md to show:
- Recent actions taken
- Artifacts processed
- Status changes
3. Determine Available Next Steps
Read references/orchestration-map.md to:
- Identify artifacts with status "approved" whose dependent skills haven't started
- Find all "not started" artifacts with satisfied dependencies
- List available immediate next steps
4. Check Scheduled Tasks Status
If scheduled tasks exist at config/scheduled-tasks.md:
- List all 5 tasks (weekly-status, daily-deviation, risk-update, sync-streams, executor-reminders)
- Show enabled/disabled status
- Show last run timestamp if available
- Show next scheduled run time
5. Display Status Summary
Present to user in this format:
# Project Status Report
## Current Phase
Phase [N] of 5: [Phase Name]
## Artifact Summary
- Completed: X artifacts
- In Progress: Y artifacts
- Approved (pending execution): Z artifacts
- Not Started (dependencies met): W artifacts
- Not Started (blocked): V artifacts
## Recent Activity (Last 10 actions)
[Display table with timestamp, artifact, status, notes]
## Scheduled Tasks Status
- weekly-status: [ENABLED/DISABLED] | Last run: [DATE] | Next: [DATE]
- daily-deviation: [ENABLED/DISABLED] | Last run: [DATE] | Next: [DATE]
- risk-update: [ENABLED/DISABLED] | Last run: [DATE] | Next: [DATE]
- sync-streams: [ENABLED/DISABLED] | Last run: [DATE] | Next: [DATE]
- executor-reminders: [ENABLED/DISABLED] | Last run: [DATE] | Next: [DATE]
## Recommended Next Steps
1. [Step 1 with rationale and artifact reference]
2. [Step 2 with rationale and artifact reference]
3. [Step 3 with rationale and artifact reference]
---
Use `/next-step` to get detailed guidance on the recommended next action.
Use `/init-project` to create a new project.
Use `/sprint-report` to generate a weekly status report for Phase 3+.
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.
- 6d ago First seen · 90 lines · 8 tokens per session scan A 9eb45765adc4
status is a command published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 634 once invoked, about $0.0000 per session on Opus 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.
client-update
Write a clear, reassuring client progress update from a few notes about where the job stands.
run-event-workflow
Manage event registrations, reminder cadence, post-event follow-up, and participation reporting.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.