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/next-step)<a href="https://agentmods.dev/commands/kirkruglov/claude-project-manager/next-step"><img src="https://agentmods.dev/badge/commands/kirkruglov/claude-project-manager/next-step.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.00009 | $0.00660 |
| Opus 5 | $0.00005 | $0.00330 |
| Sonnet 5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
next-step 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 7d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Step
Analyze project state and orchestration rules to recommend the immediate next action.
Process
1. Read Project State
Read project-state.md to get:
- Current phase
- Status of all 34 artifacts
- Which artifacts are "approved", "in_progress", "not started"
2. Read Orchestration Map
Read references/orchestration-map.md to understand:
- Artifact dependencies (which artifacts must complete before others can start)
- Skill-to-artifact mapping (which skills produce which artifacts)
- Phase progression rules
- Blocking conditions for phase transitions
3. Identify Available Next Steps
For each artifact with status "approved":
- Check if all dependent prerequisites have status "completed"
- If yes, that artifact is "ready to execute"
For each artifact with status "not started":
- Check if all dependencies have status "approved" or "completed"
- If yes, and no other blocker exists, that artifact is "available to start"
4. Validate Input Data
For each available artifact:
- Check if required input data exists in
input/folder - Verify data completeness (no critical missing fields)
- If data is missing, flag as "blocked pending input"
5. Present Recommendations
Display 1-3 recommended next steps in priority order:
# Recommended Next Steps
## Priority 1: [Artifact Name] (ID: #X)
**Status**: [Ready to execute / Available to start / Blocked]
**Skill**: [Skill name from orchestration map]
**Dependencies**: [All satisfied / Missing Y, Z]
**Rationale**: [Why this is the next logical step]
**Action**:
- If ready: "Run skill [skill-name] now"
- If blocked: "Waiting for [artifact] or [input file] — see requirements below"
---
## Priority 2: [Artifact Name] (ID: #Y)
[Same format]
---
## Priority 3: [Artifact Name] (ID: #Z)
[Same format]
---
## Blocking Issues (if any)
- [Issue 1]: Cannot proceed to Phase N without artifact #M
- [Issue 2]: Missing input: [file name] required for artifact #X
6. Offer Confirmation
If user confirms the recommended step:
- Extract skill name
- Trigger skill with appropriate parameters
- Pass
artifact_id,phase,project_pathto the skill - Update project-state.md upon skill completion
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.
- 7d ago First seen · 103 lines · 9 tokens per session scan A 7863387688cf
next-step is a command published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 660 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.
run-event-workflow
Manage event registrations, reminder cadence, post-event follow-up, and participation reporting.
client-update
Write a clear, reassuring client progress update from a few notes about where the job stands.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.