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 product-messaging-playbookgit 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/product-messaging-playbook)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/product-messaging-playbook"><img src="https://agentmods.dev/badge/skills/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/skills/stefanoskarakasis/product-marketing-skills/product-messaging-playbook"><img src="https://agentmods.dev/badge/skills/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.00099 | $0.04984 |
| Opus 5.5 | $0.00040 | $0.01994 |
| Sonnet 5.5 | $0.00020 | $0.00997 |
| Haiku 4.5 | $0.00010 | $0.00498 |
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 11d 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Messaging Playbook
The document a PMM hands to Sales and CS so they can talk about a new
product or feature the same day it ships — not a strategy deck, not raw
brain output, but one assembled artifact: what the problem is, why the
product solves it, how it compares to the one alternative buyers actually
ask about, and exactly what to say (and not say) on a call. It doesn't
derive positioning, pillars, or proof — those already have owners
(positioning-messaging, message-house, proof-points). This skill
reads their output and the brain, asks only for what's genuinely new
(the problem framing and forward-looking targets for this feature), and
assembles the rest into one document a rep can open cold.
Trigger
- When: A PMM needs a single Sales/CS-facing document for a specific product or feature — new or existing — that bundles the problem it solves, the pitch, one named competitive comparison, and a discovery/objection script, in a format non-PMMs can use without translation.
- Not for: Deriving the underlying positioning statement or messaging
hierarchy →
positioning-messaging, run first. Formatting general company-level positioning into a Roof + Pillars table with no feature-specific problem framing or sales script →message-housealready does that; use this skill instead when the ask specifically includes discovery questions, objection handling, or a named-competitor comparison. Sourcing or auditing the proof points themselves →proof-points, run first if Section 6 is thin. Building a full multi-competitor battlecard, not a single named comparison scoped to one feature →competitive-battlecard(in thepmm-competitive-intelligenceplugin); this skill's Section 3 is intentionally scoped to one alternative, not a full battlecard. - Example prompts:
- "Build a messaging playbook for [feature]"
- "Give sales something they can use for this launch"
- "I need a handoff doc for sales and CS on [product]"
- "Solution guide for [feature] vs [competitor]"
- "Turn this into something a rep can read cold"
What ships with it
1 file 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.
- 11d ago Changed · -1 lines · -10 tokens per session a17856e02340
- 15d ago Changed · +1 lines a8ce67de45dd
- 18d ago Changed 892e48d53eb1
- 19d ago Changed · +2 lines 0c611c704dc7
- 20d ago Changed · +15 lines e18edf893c59
- 25d ago Changed · +13 lines 8dfa0586eced
- 28d ago First seen · 376 lines · 109 tokens per session scan A 1a25716030e8
product-messaging-playbook is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 99 tokens to every session and 4,984 once invoked, about $0.0004 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 skills, from other repositories
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.