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-marketing-contextgit 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-marketing-context)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/product-marketing-context"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/product-marketing-context/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-marketing-context"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/product-marketing-context.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.00090 | $0.02391 |
| Opus 5 | $0.00045 | $0.01196 |
| Sonnet 5 | $0.00018 | $0.00478 |
| Haiku 4.5 | $0.00009 | $0.00239 |
Grade A, and why
product-marketing-context 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 12d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Marketing Context (The Brain)
Stop re-explaining your company, your buyer, and your competitors to every tool you use. Answer these questions once, in about 15 minutes, and every other skill in this stack reads the answers automatically instead of asking again.
Trigger
- When: Building the GTM brain for the first time, editing a section, or running a health audit on the existing brain.
- Not for: Any skill that reads the brain rather than builds it — every brain-dependent skill in this stack routes here first if the brain is missing, then uses its own Trigger. This skill has no downstream overlap since it is upstream of everything else.
- Example prompts:
- "Build my brain"
- "Set up my GTM foundation"
- "Audit my brain"
- "Update my ICP"
- "Check brain health"
Inputs
- Args: None required — the wizard (Step 2) asks one question at a time. A pitch deck, pricing page, or win/loss doc pasted in advance speeds this up but isn't required.
- Defaults: No brain found → start the wizard from Section 1. Brain exists → load silently and offer [View current] [Edit a section] [Run health audit].
- Context keys:
/foundation/brain.md— read if it exists (load silently, skip answered sections); written to, section by section, only after user confirmation..agents/*.md,.claude/*.md— optional legacy files; offered for migration if found.- Brain contract: Reads all 6 sections if present. Writes: any section, but only after explicit user confirmation of the exact before/after (Operating Rule 1).
Pre-flight
- Check
/foundation/brain.md— see Step 1 (Detect Brain State). - Check for legacy files (
.agents/*.md,.claude/*.md) and offer migration if found. - No hard block: this skill is the entry point for users with no brain at all.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PRODUCT MARKETING CONTEXT │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: product, ICP, alternatives, voice, market, │
│ proof points — one section at a time │
│ ✓ Output: /foundation/brain.md, confirmed section by section │
│ ✓ Pushes back on vague answers before storing them │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Docs/Drive: pulls company overview and product facts │
│ + CRM: pulls win/loss reasons and deal data to sharpen ICP │
└─────────────────────────────────────────────────────────────────┘
What ships with it
7 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.
- 12d ago First seen · 221 lines · 90 tokens per session scan A e51b99ddc933
product-marketing-context is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (5 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 2,391 once invoked, about $0.0005 per session on Opus 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 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…