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.
git clone --depth 1 https://github.com/pmprompt/claude-plugin-product-managementWrote 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/pmprompt/claude-plugin-product-management/competitive-intel)<a href="https://agentmods.dev/commands/pmprompt/claude-plugin-product-management/competitive-intel"><img src="https://agentmods.dev/badge/commands/pmprompt/claude-plugin-product-management/competitive-intel.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.00000 | $0.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
competitive-intel 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 7d 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.
What it actually says
/competitive-intel — Competitive Intelligence Workflow
Deep competitive analysis from positioning to strategic moats.
What It Does
Chains competitive analysis, power dynamics, and positioning to understand your competitive landscape and identify differentiation opportunities.
When to Use
- Entering new market or category
- Repositioning against competitors
- Strategic planning cycle
- Investor or board presentation prep
Workflow
-
Competitive Analysis — Map competitors' strengths, weaknesses, and positioning (uses
competitive-analysis-frameworkskill) -
7 Powers — Identify competitors' power sources and your opportunities (uses
seven-powersskill) -
Positioning Canvas — Clarify your unique differentiation (uses
positioning-canvasskill)
Usage
/competitive-intel [market or category]
Example:
/competitive-intel Design tool market (Figma, Sketch, Adobe XD)
Output
- Competitive landscape map
- Competitor strengths/weaknesses analysis
- 7 Powers assessment (who has which powers)
- Recommended positioning and differentiation strategy
Next Steps After /competitive-intel
/strategy— Build full strategic narrative/pricing— Competitive pricing analysis- Update positioning on website and sales materials
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.
- 7d ago First seen · 47 lines · 0 tokens per session scan A 4caf3c90d717
competitive-intel is a command published in the GitHub repository pmprompt/claude-plugin-product-management (48 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 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 commands, from other repositories
workflow-design-sprint
Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call).
workflow-foundation-sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis).
chain
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator).
workflow-foundation-to-design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff.
workflow-post-launch-learning
Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons).
workflow-customer-discovery
Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem).