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/refresh-brain)<a href="https://agentmods.dev/commands/stefanoskarakasis/product-marketing-skills/refresh-brain"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/refresh-brain/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/refresh-brain"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/refresh-brain.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.00013 | $0.00229 |
| Opus 5.5 | $0.00005 | $0.00092 |
| Sonnet 5.5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
refresh-brain 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 4d 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
/refresh-brain — Refresh Your Brain
Runs the product-marketing-context skill's Step 6 (Refresh Stale Fields): compares every field's date with its section's freshness limit, lists what is stale, and asks one field at a time whether it is still true, changed, or should be dropped.
Invocation
- /refresh-brain
- /refresh-brain 3
Workflow
Step 1: Check Brain State
Apply the product-marketing-context skill's Step 1 (Detect Brain State). With no brain, say so and offer to build one.
Step 2: Refresh
Follow the skill's Step 6 exactly. If a section number was passed, check only that section. This command is a thin entry point; the behavior lives in product-marketing-context/SKILL.md. If the two ever disagree, the skill file is correct and this command should be updated to match.
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.
- 4d ago First seen · 24 lines · 13 tokens per session scan A 0ad7800792c1
refresh-brain is a command published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (7 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 229 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-12.
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.
retro
Run a post-ship retrospective — measure outcomes vs. predictions, extract lessons, update memory, and feed insights back into the PM system.
onboarding
Set up PM Copilot — a guided wizard that builds your persistent memory profile so every future session is grounded in your product context.
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.