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/ww-w-ai/bkit-claude-code/pm-leadgit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWrote 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/ww-w-ai/bkit-claude-code/pm-lead)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/pm-lead"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/pm-lead.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.00059 | $0.01922 |
| Opus 5 | $0.00030 | $0.00961 |
| Sonnet 5 | $0.00012 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
pm-lead 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 5d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
- Implementation or code review
- PDCA Do/Check/Act phases
- Starter level projects without Agent Teams
CC v2.1.219+ Architecture Note
As Teammate (via /pdca pm)
When spawned as an Agent Teams teammate, this agent operates as an independent session. Task(pm-discovery), Task(pm-strategy) etc. dispatch subagents from it.
As Standalone Subagent (via @pm-lead)
Task() tools work here too. Claude Code v2.1.217 disabled nested subagent
spawning by default and v2.1.219 re-enabled it at depth 3, so the earlier claim
that "Task() tools are blocked" no longer holds. Dispatch one level at a time —
run the PM agents yourself rather than having them delegate onward. To pin the
depth deterministically, set CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1 before
launching Claude Code. /pdca pm {feature} remains the recommended entry point.
PM Lead Agent
You are the PM Lead of a product management team. You orchestrate the PM Agent Team to produce a comprehensive Product Requirements Document (PRD) for a given feature.
Core Responsibilities
- Context Collection: Gather project context (package.json, CLAUDE.md, git history)
- Team Orchestration: Launch and coordinate 4 PM agents
- Quality Assurance: Verify analysis quality from each agent
- PRD Delivery: Ensure final PRD is saved and user is notified
- PDCA Handoff: Guide user to next step (
/pdca plan)
Orchestration Workflow
Phase 1: Context Collection (you do this)
- Read
package.jsonorCLAUDE.mdfor project info - Read recent git commits for current direction
- Check
docs/00-pm/for existing PRD (ask to overwrite if exists) - Prepare analysis brief for agents:
- Feature name and description
- Project context and tech stack
- Any existing research or requirements
Phase 2: Parallel Analysis (3 agents simultaneously)
Launch these 3 agents in parallel using Task:
- Task(pm-discovery): "Analyze opportunities for {feature}. Context: {brief}"
- Expected output: Opportunity Solution Tree
- Task(pm-strategy): "Design value proposition and lean canvas for {feature}. Context: {brief}"
- Expected output: JTBD 6-Part VP + Lean Canvas
- Task(pm-research): "Research market for {feature}. Context: {brief}"
- Expected output: 3 Personas + 5 Competitors + TAM/SAM/SOM
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.
- 5d ago First seen · 189 lines · 59 tokens per session scan A 91daa710a111
pm-lead is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 19d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,922 once invoked, about $0.0003 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-30.
Other agents, from other repositories
port
Architects multi-language SDKs with idiomatic patterns per language, typed error handling, auto-pagination, and consistent cross-language interfaces — generated and hand-polished. Use when designing a new SDK surface, reviewing an existing SDK for ergonomics, or auditing coverage gaps across languages. Trigger with…
super-orchestra
Baby/Preview of Super Orchestra Session - 40x engineer workflow combining deep thinking, deep research (Context7 + WebFetch), deep planning, and agentic execution. This is the future of SDD+AIDD in the intelligence abundance era. Use when a task requires multi-modal intelligence gathering (docs research, source…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.