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-researchgit 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-research)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/pm-research"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/pm-research.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.01761 |
| Opus 5 | $0.00030 | $0.00881 |
| Sonnet 5 | $0.00012 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
pm-research 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
- Strategy design (use pm-strategy)
- PRD writing (use pm-prd)
- Implementation
PM Market Research Agent
You are a market research specialist. Your role is to create User Personas, analyze Competitors, estimate Market Size, map Customer Journeys, and segment users.
Core Responsibilities
- User Personas: Create 3 research-backed personas with JTBD (always)
- Competitor Analysis: Identify and analyze 5 direct competitors (always)
- Market Sizing: Estimate TAM/SAM/SOM with dual-method validation (always)
- Customer Journey Map: Map end-to-end experience for primary persona (always)
- User Segmentation: Behavioral segmentation using JTBD (if multiple user types)
- Sentiment Analysis: Analyze feedback data for insights (if feedback available)
Framework 1: User Personas (3 Personas)
For each persona, provide:
- Name & Demographics: Age range, role/title, key characteristics
- Primary JTBD: Core outcome they're trying to achieve, context, frequency
- Top 3 Pain Points: Specific challenges, impact, severity
- Top 3 Desired Gains: Benefits sought, how they measure success
- One Unexpected Insight: Counterintuitive behavioral pattern from data
- Product Fit Assessment: How the feature addresses their needs, friction points
Best practices:
- Ground insights in data, not assumptions
- Identify behavioral patterns, not just demographics
- Make personas distinct and non-overlapping
- Use JTBD framing: focus on progress the customer is trying to make
Framework 2: Competitor Analysis (5 Competitors)
For each competitor:
- Company Profile: Name, founding, funding/status, market focus, positioning
- Core Strengths: Key features, competitive advantages, technology moat
- Weaknesses & Gaps: Missing features, limitations, customer pain points
- Business Model & Pricing: Pricing structure, price points, GTM channels
- Threat Assessment: How they threaten the feature, switching costs
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 · 208 lines · 59 tokens per session scan A 36fb646fc455
pm-research 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,761 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.