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 skills add ww-w-ai/bkit-claude-code --skill pm-discoverygit 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/skills/ww-w-ai/bkit-claude-code/pm-discovery)<a href="https://agentmods.dev/skills/ww-w-ai/bkit-claude-code/pm-discovery"><img src="https://agentmods.dev/badge/skills/ww-w-ai/bkit-claude-code/pm-discovery.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00872 |
| Opus 5 | $0.00039 | $0.00436 |
| Sonnet 5 | $0.00016 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
pm-discovery 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Agent Team - Product Discovery & Strategy
Automated PM analysis pipeline: Discovery + Strategy + Research -> PRD Based on pm-skills by Pawel Huryn (MIT License)
Overview
PM Agent Team provides AI-powered product management analysis for solo developers and small teams without a dedicated PM. It runs before the PDCA Plan phase to ensure you're building the right thing.
How It Works
/pdca pm {feature}
|
v
PM Lead (fable) - orchestrates
|
+-- pm-discovery --> Opportunity Solution Tree
+-- pm-strategy --> Value Proposition + Lean Canvas [parallel]
+-- pm-research --> Personas + Competitors + Market
|
v
pm-prd --> Beachhead + GTM + PRD (8-section)
|
v
docs/00-pm/{feature}.prd.md
|
v
Next: /pdca plan {feature} (PRD auto-referenced)
Included PM Frameworks (8)
| Framework | Agent | Origin |
|---|---|---|
| Opportunity Solution Tree | pm-discovery | Teresa Torres |
| Value Proposition (JTBD 6-Part) | pm-strategy | Huryn & Abdul Rauf |
| Lean Canvas | pm-strategy | Ash Maurya |
| User Personas (JTBD) | pm-research | JTBD-based |
| Competitor Analysis | pm-research | Strategic positioning |
| Market Sizing (TAM/SAM/SOM) | pm-research | Dual-method |
| Beachhead Segment | pm-prd | Geoffrey Moore |
| GTM Strategy | pm-prd | Product Compass |
Usage
# Run PM analysis
/pdca pm my-saas-app
# After PM analysis, continue with PDCA
/pdca plan my-saas-app # PRD auto-referenced
/pdca design my-saas-app
/pdca do my-saas-app
Requirements
- Agent Teams enabled:
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 - Project level: Dynamic or Enterprise (Starter not supported)
PDCA Integration
[PM] --> [Plan] --> [Design] --> [Do] --> [Check] --> [Act] --> [Report]
^ ^
new PRD auto-referenced in Plan
When /pdca plan {feature} runs after PM analysis:
- Checks for
docs/00-pm/{feature}.prd.md - If found, reads PRD and uses as context for Plan document
- Plan document quality is significantly improved with PM-backed data
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 · 114 lines · 78 tokens per session scan A ce21fda63845
pm-discovery is a skill published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 2d ago), licensed Apache-2.0. It adds 78 tokens to every session and 872 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-09-03.
Other skills, from other repositories
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
summon
Autonomous orchestrator for manifest work items through the development lifecycle. Use when running egregore to process a backlog automatically.
sales-expert
Build comprehensive sales technology solutions including CRM implementation, pipeline management, sales forecasting, and performance analytics. Use when the user mentions CRM, sales pipelines, lead qualification, opportunity tracking, sales forecasting, quotas or territories, or sales automation.
create-backlog
Creates backlog epics in issue tracker from a specification document.
publish
Creates a PR and updates issue tracker states (auto-detects mode from branch name).
implement-feature
Implements a feature from the issue tracker -- spec, design, fix, review, test, publish.