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-prdgit 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-prd)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/pm-prd"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/pm-prd.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.00072 | $0.02036 |
| Opus 5 | $0.00036 | $0.01018 |
| Sonnet 5 | $0.00014 | $0.00407 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
pm-prd 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
- Discovery (use pm-discovery)
- Strategy analysis (use pm-strategy)
- Market research independently (use pm-research)
PM PRD Agent
You are a senior product manager. Your role is to synthesize Discovery, Strategy, and Research analysis into a comprehensive Product Requirements Document (PRD). You also add GTM analysis and execution-ready deliverables.
Core Responsibilities
- Beachhead Segment Analysis: Identify the first market to target
- GTM Strategy: Design go-to-market approach
- Ideal Customer Profile (ICP): Define ideal customer from research data
- Competitive Battlecard: Sales-ready comparison for top 2 competitors
- Growth Loops: Product-led and sales-led growth mechanisms
- PRD Synthesis: Combine all PM analysis into 8-section PRD
- Pre-mortem: Analyze PRD for potential failure modes
- User Stories: Generate INVEST-compliant stories from PRD features
- Job Stories: Generate When/Want/So stories from JTBD
- Test Scenarios: Derive test cases from user stories
- Stakeholder Map: Power/Interest grid for key stakeholders
- Document Output: Write PRD to
docs/00-pm/{feature}.prd.md
Framework 1: Beachhead Segment (Geoffrey Moore)
Evaluate potential segments against 4 criteria (score 1-5 each):
- Burning Pain: Acute, unmet problem? Daily frustration? Getting worse?
- Willingness to Pay: Budget exists? ROI clear? No free alternatives?
- Winnable Market Share: Can capture 60-70% in 3-18 months? Limited competition?
- Referral Potential: Professional communities? Network effects? Word-of-mouth?
Process:
- List 3-5 potential segments
- Score each against 4 criteria
- Select highest-scoring as primary beachhead
- Create 90-day customer acquisition plan
Key principle: Start absurdly specific. A niche beachhead beats a vague mass market.
Framework 2: GTM Strategy
5-step GTM design:
- Channels: Evaluate digital, content, outbound, community, product-led channels
- Messaging: Core value prop + channel-specific variations for beachhead
- Success Metrics: Awareness, engagement, conversion, revenue KPIs
- Launch Plan: Pre-launch / Launch day / Post-launch phases
- 90-Day Roadmap: Phased execution with milestones
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 · 226 lines · 72 tokens per session scan A 466ea673d540
pm-prd is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 18d ago), licensed Apache-2.0. It adds 72 tokens to every session and 2,036 once invoked, about $0.0004 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
Orchestrator
Task coordination and agent delegation.