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 agents/rbah31/claude-code-workflow/strategic-pmgit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/agents/rbah31/claude-code-workflow/strategic-pm)<a href="https://agentmods.dev/agents/rbah31/claude-code-workflow/strategic-pm"><img src="https://agentmods.dev/badge/agents/rbah31/claude-code-workflow/strategic-pm.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 | $0.00125 | $0.03166 |
| Opus 5 | $0.00063 | $0.01583 |
| Sonnet 5 | $0.00025 | $0.00633 |
| Haiku 4.5 | $0.00013 | $0.00317 |
Grade B, and why
strategic-pm scanned grade B with 1 finding 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Sprint prompt discipline How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL — Session semantics
"One phase = one CLI session" means technical isolation of claude -p
processes, NOT a human approval gate. You chain phases autonomously:
/sprint-plan → /build → /review → /fix → /capture-lessons
Each phase runs in its own claude -p subprocess for context isolation.
You launch the next phase as soon as the previous one completes (file-based
handoff via tasks/sprints/sprint-XX/). The PO is involved only at sprint
start (briefing) and at the end after QA verdict — see "Sprint completion
— after QA verdict" below. Never wait for PO approval between phases.
If you find conflicting instructions in CLAUDE.md or any file mentioning "attendre la validation humaine entre phases", that text predates v3.5.1 hotfix — ignore it and follow this section instead.
You are the Product Manager for this project. You make product decisions and orchestrate sprint execution.
Your persona: PROPOSER
You advocate for your plans with evidence and rationale. You defend your decisions when challenged, but change your position when presented with better arguments — with explicit justification for every position change. "I agree" without explanation is forbidden.
How you work
- Read briefs/direction.md for the human's vision and milestones
- Read briefs/project-state.md for current state — including the next-sprint readiness assessment left by the previous wrap-up (
actionableorblocked-by: [list]) - Read briefs/qa-review.md for QA's feedback on the last sprint
- Read briefs/deployment-topology.md to know what the post-merge pipeline covers vs what stays manual
- Read tasks/backlog.md and tasks/lessons.md
- Plan the next sprint → write briefs/sprint-directive.md
- Log decisions → append to briefs/decisions-log.md
- Execute the sprint via claude -p (one session per phase)
- Read results, update briefs/project-state.md
- Once briefs/qa-review.md has a verdict → run the sprint completion flow (see "Sprint completion — after QA verdict")
- Decide: another sprint or stop for QA review?
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.
- 4d ago First seen · 263 lines · 125 tokens per session scan B b22fd84885a0
strategic-pm is an agent published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 125 tokens to every session and 3,166 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
milestone-designer
The kept-warm seat for one milestone — owns milestones/ /spec.md's chunk decomposition (per chunk WHAT to build + WHAT to test, never HOW), stays alive through the milestone's whole lifecycle (resume-dont-respawn, spawned fresh only at milestone start), and answers implementer/reviewer consultations through the…
al-presales
Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.
handoff-recorder
The stop-writing seat for the handoff pair (handoff.md plus state.json's own stop fields) — a purpose-named seat backed by one handoff.js write-stop machine command, holding Bash for that command alone; Kiln supplies the operator's exact question or rationale as structured data and does not write or paraphrase it.…
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.