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/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/commands/stefanoskarakasis/product-marketing-skills/product-messaging-playbook)<a href="https://agentmods.dev/commands/stefanoskarakasis/product-marketing-skills/product-messaging-playbook"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/product-messaging-playbook/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/stefanoskarakasis/product-marketing-skills/product-messaging-playbook"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/product-messaging-playbook.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.00417 |
| Opus 5.5 | $0.00012 | $0.00167 |
| Sonnet 5.5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
product-messaging-playbook 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 13d 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
/pmm-positioning:product-messaging-playbook -- Product Messaging Playbook
Assembles the one document Sales and CS actually need — problem framing, story, a comparison against the one competitor buyers ask about, and a discovery/objection script — from what already exists in the brain and your other skills' output. Does not derive positioning, pillars, or proof itself; if those don't exist yet, it says so and points at positioning-messaging, message-house, or proof-points first.
Invocation
/pmm-positioning:product-messaging-playbook Build a playbook for our new automations feature
/pmm-positioning:product-messaging-playbook [feature name] vs Breezy HR
/pmm-positioning:product-messaging-playbook [paste a message-house output] now build the full playbook
Workflow
Uses the product-messaging-playbook skill. Loads brain Sections 1, 2, 3, 5, 6 (or pasted message-house/positioning-messaging output, which takes precedence for any field it covers), asks fresh for feature-specific fields the brain doesn't and shouldn't hold (problem framing, forward-looking success targets, keywords, packaging), labels every unmeasured target [TARGET — not yet measured] so it's never mistaken for sourced proof, builds a named-competitor comparison only when a competitor is explicitly given, and returns one markdown deliverable — Messaging Foundation, Story, Comparative Positioning (if built), Sales Enablement Kit, plus a "Still needed" list. Blocks and redirects to positioning-messaging or product-marketing-context if no usable positioning exists yet.
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.
- 13d ago First seen · 21 lines · 31 tokens per session scan A 894592d0b49e
product-messaging-playbook is a command published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (7 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 417 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-10-03.
Other commands, from other repositories
brief-me
Get briefed — loads your full memory, pulls live state from all connected tools, surfaces risks, staleness, upcoming milestones, and gives you a prioritized briefing so you're never starting blank.
design-ai-feature
Design an AI-powered feature end-to-end — model selection, prompt architecture, eval framework, failure modes, cost modeling, and improvement flywheel.
competitive-intel
Run a competitive intelligence analysis — landscape mapping, battlecards, 7 Powers moat comparison, positioning gaps, and monitoring plan.
discover
Run a full discovery cycle — problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and OST mapping — from a rough idea to validated opportunity.
plan-launch
Plan a full go-to-market launch — positioning, messaging hierarchy, ICP definition, launch timeline, rollback plan, and post-launch measurement.
retro
Run a post-ship retrospective — measure outcomes vs. predictions, extract lessons, update memory, and feed insights back into the PM system.