phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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 commands/phuryn/pm-skills/competitive-analysisgit clone --depth 1 https://github.com/phuryn/pm-skillsWrote 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/commands/phuryn/pm-skills/competitive-analysis)<a href="https://agentmods.dev/commands/phuryn/pm-skills/competitive-analysis"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/competitive-analysis.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.1 | $0.00016 | $0.00759 |
| Opus 5 | $0.00008 | $0.00380 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
competitive-analysis 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- competitive-analysis — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/competitive-analysis -- Competitive Landscape Analysis
Research and analyze your competitive landscape. Identifies direct and indirect competitors, maps positioning, and surfaces differentiation opportunities.
Invocation
/competitive-analysis AI-powered project management tools
/competitive-analysis Our product vs Notion, Asana, and Monday.com
/competitive-analysis [upload a competitor list or market brief]
Workflow
Step 1: Understand the Competitive Context
Ask:
- What is your product? What category does it compete in?
- Any specific competitors you want analyzed? Or should I identify them?
- What's the lens? (feature comparison, positioning, pricing, go-to-market)
- What will you use this analysis for? (strategy, sales enablement, investor pitch, product roadmap)
Step 2: Identify Competitors
Apply the competitor-analysis skill:
- Identify 5 direct competitors (same category, same buyer)
- Identify 2-3 indirect competitors (different approach, same job-to-be-done)
- Note emerging/disruptive players if relevant
- Use web research to gather current information
Step 3: Analyze Each Competitor
For each competitor:
- Positioning: How they describe themselves, target audience, key messaging
- Strengths: What they do well, where they win
- Weaknesses: Where they fall short, common complaints
- Pricing: Model and price points (if public)
- Market traction: Funding, team size, customer base signals
- Recent moves: New features, partnerships, pivots
Step 4: Generate Competitive Analysis
## Competitive Analysis: [Your Product/Market]
**Date**: [today]
**Analyzed**: [count] competitors
### Market Overview
[2-3 sentences on market dynamics, trends, and where it's heading]
### Competitive Landscape
| Competitor | Category | Target | Positioning | Strength | Weakness |
|-----------|----------|--------|------------|----------|----------|
### Feature Comparison Matrix
| Capability | Your Product | Competitor A | Competitor B | Competitor C |
|-----------|-------------|-------------|-------------|-------------|
### Positioning Map
[2x2 matrix showing competitive positioning on key dimensions]
### Differentiation Opportunities
1. **[Opportunity]** — [why it's defensible and valuable]
2. ...
### Competitive Threats
1. **[Threat]** — [what to watch for, recommended response]
2. ...
### Recommendations
- **Double down on**: [your unique advantages]
- **Close the gap on**: [table-stakes features you're missing]
- **Ignore**: [competitor moves that aren't worth responding to]
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.
- 6d ago First seen · 98 lines · 16 tokens per session scan A 115f596c5774
competitive-analysis is a command published in the GitHub repository phuryn/pm-skills (26,001 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 759 once invoked, about $0.0001 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 commands, from other repositories
value-prop-statements
Fan an existing positioning statement out into segment- and channel-specific value-prop copy variants, trace-checked against drift.
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
positioning-messaging
Build or audit positioning statements, messaging, and related output.
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.
brand-voice
Build a persona-adaptive voice guide — brand attributes, tone by buyer and channel, forbidden language — then deepen brain Section 4.