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 skills/aakashg/pm-claude-code-setup/competitive-analysisnpx skills add aakashg/pm-claude-code-setup --skill competitive-analysisgit clone --depth 1 https://github.com/aakashg/pm-claude-code-setupWrote 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/aakashg/pm-claude-code-setup/competitive-analysis)<a href="https://agentmods.dev/skills/aakashg/pm-claude-code-setup/competitive-analysis"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-code-setup/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 | $0.00000 | $0.00510 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Trigger
Activate on "analyze competitor", "competitive analysis", "compare us to [company]".
Behavior
Step 1: Get Context
Ask:
- Which competitor?
- Which product or feature to analyze?
- What's our product for comparison?
Step 2: Analyze
What They Built
- Core functionality
- Target user
- Key differentiator
What's Smart
- 3 decisions they nailed and why
What's Weak
- 3 gaps or missed opportunities
Implications for Us
- What to copy, what to avoid, where to differentiate
Example
Bad analysis (vague, no evidence):
What's Smart:
- They have a good product
- Nice onboarding
- Growing fast
What's Weak:
- Some features are missing
- Could be cheaper
Good analysis (specific, actionable):
What's Smart:
1. Freemium with usage-based upgrade trigger — free users hit the
5-project limit naturally around week 3, right when switching cost
is highest. Conversion to paid: ~8% (industry avg: 3-5%).
2. API-first architecture — 400+ integrations in marketplace. This
creates lock-in that pure UX improvements can't match.
3. AI summarization launched Q3 — not better than competitors, but
they embedded it in the daily workflow (auto-summary after every
meeting) instead of making it a standalone feature.
What's Weak:
1. Enterprise pricing is opaque — requires "contact sales" for teams
over 50. Mid-market buyers (our sweet spot) hate this. Opportunity:
transparent pricing up to 200 seats would win deals they lose.
2. Mobile app is read-only for most features — 34% of their App Store
reviews mention this. Their mobile MAU/DAU ratio is 0.3 vs. 0.6 on
desktop. Opportunity: mobile-first editing.
3. No audit trail for compliance — dealbreaker for fintech and healthcare
segments. They lose these verticals entirely.
Rules
- Be specific. "Great UX" is useless. Name the interaction that works and why.
- Flag unknowns with [NEED: more info on X]
- Analyze product decisions, not visual design opinions
- Include numbers: pricing, conversion rates, market share, review counts. Data beats opinion.
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 · 72 lines · 0 tokens per session scan A 8a13dee54949
competitive-analysis is a skill published in the GitHub repository aakashg/pm-claude-code-setup (152 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 510 tokens. 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 skills, from other repositories
kimchi
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to…
create-slide-deck
Create beautiful HTML slide decks for product presentations. Reads product context, extracts brand colors from websites, and generates self-contained HTML files with keyboard navigation and print-friendly layouts.
pm-setup
Interactive onboarding wizard that creates the PM-OS knowledge base for your product. Asks questions, fetches company info, and populates all knowledge files.
opportunity-assessment
Validate ideas with market sizing (TAM/SAM/SOM), competitive landscape, strategic alignment, technical feasibility, and a go/no-go recommendation.
pm-os
Product Manager's Operating System: gateway skill that routes requests to 27 PM workflow skills and manages the knowledge system.
sprint-scope
Sprint planning with capacity awareness. Pulls from backlog (via MCP or manual input), calculates what fits based on team velocity, and outputs recommended scope with stretch goals and deferred items.