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 retrogit 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/retro)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/retro"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/retro/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/retro"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/retro.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.00085 | $0.03286 |
| Opus 5 | $0.00043 | $0.01643 |
| Sonnet 5 | $0.00017 | $0.00657 |
| Haiku 4.5 | $0.00009 | $0.00329 |
Grade A, and why
retro 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
retro — GTM Retrospective Engine for PMMs
Runs a structured retrospective for cross-functional squads that produces OKR-linked decisions. Not a feelings circle. A diagnostic system.
Trigger
- When: Post-launch review, GTM cycle debrief, sprint retrospective with a PMM lens, or any cross-functional session where decisions are needed, not just discussion.
- Not for: Pre-launch risk analysis → use
pre-mortem. OKR setting for the next quarter → usepmm-okrs. Campaign briefing after a retro surfaces a messaging gap → usegaccs-brief. Competitive root cause analysis → no dedicated skill yet. - Example prompts:
- "Run a retro on our Q2 product launch"
- "We missed our pipeline KR — let's debrief"
- "What went wrong with the enterprise campaign?"
- "Facilitate our post-launch review for the analytics dashboard"
- "Our last sprint ended badly — help us figure out why"
Inputs
- Args: Cycle name or launch name (required). Free format — one sentence minimum.
- Defaults: If no cycle named, run intake before proceeding. Never generate a retro output without a named cycle and at least one OKR to anchor to.
- Context keys:
/foundation/brain.md— optional but recommended. Load ICP, Positioning, Revenue Levers, GTM Motion, Launch Tier Definitions silently if present./context/meta-patterns.md— optional; recurring patterns the user has logged from all skills.
Pre-flight
Before anything else, check /foundation/brain.md.
If it exists — load silently. Extract:
- Section 2 (ICP Definition) → shapes which failure modes are highest-stakes
- Section 3 (Alternatives & Positioning) → was the positioning coherent with this launch? Source of truth for diagnosis.
- Section 5 (Market Context) → which market forces was this initiative riding on? Root causes shift by context.
- Section 6 (Proof Points Registry) → what proof was this launch meant to generate or rely on?
Confidence awareness: If Section 3 (Alternatives & Positioning) or Section 2 (ICP Definition) is 🔴 Placeholder, flag before proceeding:
"⚠️ Positioning is marked Placeholder in your brain. This retro may surface symptoms rather than root causes — update the brain first for sharper diagnosis."
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.
- today Changed · +2 lines f34f0a0647a5
- 8d ago Changed · -1 lines 5c37dbd5aa5a
- 12d ago First seen · 283 lines · 85 tokens per session scan A 948071a77f94
retro is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (5 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 3,286 once invoked, about $0.0004 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…