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/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/pm-competitive)<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-competitive"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-competitive/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-competitive"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-competitive.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00738 |
| Opus 5.5 | $0.00012 | $0.00295 |
| Sonnet 5.5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
pm-competitive 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great-pm /pm-competitive command. Build a competitive view.
Parse arguments
<competitor-name | jtbd-slug>(required) → either a single competitor or a JTBD slug (in which case the agent enumerates the landscape).--depth=(default:quick).quick— public surface (site, docs, pricing page, recent announcements).deep— quick + user reviews + g2/capterra + estimated funnel + inferred metric movements.
Pre-flight
TARGET="${1:?usage: /pm-competitive <competitor-or-jtbd> [--depth=...]}"
mkdir -p .great-pm/drafts
Operating procedure
-
Step 0 — refine the user's query (transparent Mode B). Invoke
query-refiner-pmwith$ARGUMENTS. The refiner returns:You typed: <original> Refined to: <refined brief> What changed: <one line> Proceeding with refined. Reply "use original" to override.Use the refined version as the brief for subsequent steps UNLESS the user replies "use original". Log the refinement to
.great-pm/refinements/$(date +%Y-%m-%d).log. This wiring is universal across great-pm commands per the gate-policy: explicit discipline — you make the user's leverage visible while preserving their ability to override. -
market-analyst
- Brief: per target, gather:
- Positioning statement (theirs, in their words).
- Pricing model + tier shape.
- Core JTBD covered + where they fall short.
- Recent moves (last 90 days — launches, partnerships, pricing changes).
- Gaps we can exploit (this is the punchline).
- Things they do better than we do (the honesty section).
- If JTBD-slug, enumerate the top 3–5 competitors and apply the above per competitor, plus a comparison table at the end.
- Output:
.great-pm/drafts/competitive-brief-<target-slug>.mdusingtemplates/COMPETITIVE-BRIEF-template.md.
- Brief: per target, gather:
-
Surface the 3 positioning gaps we should consider as the one-screen summary.
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.
- 1mo ago First seen · 76 lines · 31 tokens per session scan A 8a05b9391291
pm-competitive is a command published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 738 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
CLAUDE
Multi-agent collaboration platform for persistent, proactive AI agents across rooms, workspaces, skills, and external services.
help
Quick reference for all Attune commands.
debate
Expert agents debate to find optimal solutions.
hybrid-manual
Load an existing PRD file and enter review mode. Supports JSON format with stories, priorities, dependencies, and acceptance criteria.
bug-council
Bug Council — spawn 5 diagnostic specialists in parallel to analyze a hard bug from multiple angles, then synthesize a root cause and fix recommendation.
productionos-help
Show how to use ProductionOS — explains commands, recommended workflows, best flows to run, and usage guidelines.