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 stefanoskarakasis/Product-Marketing-Skills --skill competitor-deep-divegit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/skills/stefanoskarakasis/product-marketing-skills/competitor-deep-dive)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/competitor-deep-dive"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/competitor-deep-dive/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/skills/stefanoskarakasis/product-marketing-skills/competitor-deep-dive"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/competitor-deep-dive.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.00116 | $0.07154 |
| Opus 5.5 | $0.00046 | $0.02862 |
| Sonnet 5.5 | $0.00023 | $0.01431 |
| Haiku 4.5 | $0.00012 | $0.00715 |
Grade A, and why
competitor-deep-dive 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 today.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Deep-Dive
A deep-dive is read before a decision and checked when a claim is challenged. This skill builds that document for one competitor and one decision: what they sell, what changed, what buyers and customers actually say, where we beat them, where they beat us, and what each audience should do about it. It does not keep profiles current (that is competitive-profile), does not build the one-page sales card (that is competitive-battlecard), and does not map alternatives (that is alternatives-map). It takes what those hold, adds fresh dated evidence, and proposes what it learned back into brain Section 3 for you to confirm.
Trigger
- When: A PMM, product lead or exec needs the long, sourced view of one competitor behind a named decision, or a refresh of an earlier deep-dive.
- Not for: The one-page sales card →
competitive-battlecard. Keeping five competitors' profiles current and the roster →competitive-profile. A weekly read on what changed →signal-monitor. Mapping who buyers compare you to →alternatives-map. Registering or checking a claim →proof-points. A multi-skill competitive program →workflow-orchestrator. - Example prompts:
- "Deep-dive on [competitor] for our pricing review"
- "Deep dive on [competitor] before the RFP response"
- "What do users really say about [competitor]?" (edge: reviews and deal evidence weigh most)
- "Refresh the [competitor] deep-dive" (edge: compares with the last saved deep-dive)
Inputs
- Args: The competitor (required). Optional: the decision this supports, the main audience (sales, product, exec), delivery format, depth. Missing items are asked once in Step 2.
- Notation:
Section Nalways means a brain section;Part Nmeans the numbered part of the deep-dive document (Part 4 Pricing, Part 6 Deal evidence, Part 12 Brain check). - Defaults: Decision "general reference", audience PMM, depth standard (about 2,500 body words), delivery Google Doc. A skipped answer is stated as an assumption in Check before use.
- Context keys:
/foundation/brain.md(optional, sharper with it): Sections 1 to 8, see the contract./foundation/me.md(optional): format and detail only./foundation/gaps.md(append only)./context/competitor-profiles/(newest record for this competitor, ifcompetitive-profilekeeps one),/context/deep-dives/(earlier deep-dives),/context/battlecards/,/context/signals/(last 90 days),/context/meta-patterns.md(guardrails).~~CRM,~~call recordings,~~win/loss,~~competitive intelligence,~~reviews,~~company data,~~market data,~~team chat,~~knowledge base,~~cloud storage, or pasted material.- Brain contract: Reads: Section 1 (our offerings, permitted claims, glossary), 2 (persona, pains, triggers), 3 (alternatives, status quo, why they leave, unique capabilities,
alt_shortfalls,switching_forces,objections, and the Alternatives Map block for this competitor), 4 (language preferences, forbidden phrases), 5 (why now), 6 (approved metrics, approved quotes, forbidden claims), 7 (priorities), 8 (prohibited, approvals, stakeholders). Writes: Section 3 only, as one appended Deep-Dive Field Notes block or a one-line stub, after you confirm the exact text. Never writes to: Sections 1, 2, 4, 5, 6, 7, 8.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 273 lines · 116 tokens per session scan A c3d1006c6162
competitor-deep-dive is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (7 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 7,154 once invoked, about $0.0005 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-10-16.
Other skills, from other repositories
becoming-senior-pm
Use this skill when the user asks "how do I become a senior PM", "what does senior PM actually mean", "I want to get promoted to senior", "what's the difference between PM and senior PM", "I've been a PM for 2–3 years and want to grow", "my manager says I need to work more strategically", "I'm stuck at PM level", or…
eval-suite-design
Use this skill when the user asks to "design an eval suite", "build evals for my AI feature", "create an evaluation framework", "how do I evaluate my AI", "what evals should I run", "build an eval system", or wants to create a systematic evaluation framework for an AI-powered product feature. Typically run after…
founding-pm
Use this skill when the user says "I'm the first PM", "founding PM", "I joined a startup as the only PM", "how do I set up PM processes from scratch", "no PM infrastructure exists", "I'm building the PM function", "what should a first PM do in 90 days", or is navigating the unique challenges of being an early-stage PM…
improvement-flywheel
Use this skill when the user asks about "continuous improvement for AI", "AI quality flywheel", "how do we keep improving our AI feature", "closing the eval feedback loop", "systematic AI improvement process", or wants to build a repeating process that continuously improves AI product quality over time rather than…
llm-as-judge
Use this skill when the user asks to "set up LLM as a judge", "write an LLM judge prompt", "automate quality evaluation", "use Claude to evaluate outputs", "build an automated eval", "LLM-based evaluation", or wants to create a scalable automated evaluation system where one LLM grades the outputs of another LLM.
memory
Use this skill when the user asks to "update my PM Copilot memory", "save this to my profile", "remember that", "update my context", "update my product context", "save this decision", "add this to my memory", "track this risk", "mark this risk as resolved", "add a lesson learned", "save these stakeholder notes", or…