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 product-on-purpose/pm-skills --skill iterate-retrospectivegit clone --depth 1 https://github.com/product-on-purpose/pm-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/product-on-purpose/pm-skills/iterate-retrospective)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/iterate-retrospective"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/iterate-retrospective/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/product-on-purpose/pm-skills/iterate-retrospective"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/iterate-retrospective.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00061 | $0.01114 |
| Opus 5 | $0.00030 | $0.00557 |
| Sonnet 5 | $0.00012 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
iterate-retrospective 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 9d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective
A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.
When to Use
- At the end of every sprint (for agile teams)
- After completing a significant project or milestone
- Following a major incident or outage
- When team dynamics feel off and need addressing
- At regular intervals (monthly, quarterly) even without specific triggers
- When onboarding new team members to establish improvement culture
When NOT to Use
- You want one durable learning banked for the organization -> use
iterate-lessons-log; the retro is the ceremony, the log entry outlives it - You are scoring an OKR cycle at close -> use
measure-okr-grader - The reflection must end in a pivot-or-persevere call -> use
iterate-pivot-decision - You need a recap of a general (non-retro) meeting -> use
foundation-meeting-recap
Instructions
When asked to facilitate or document a retrospective, follow these steps:
-
Set the Context Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.
-
Choose a Format Select a retrospective format that fits the team's needs. Common options include:
- Start/Stop/Continue: Simple and direct
- 4Ls: Liked, Learned, Lacked, Longed for
- Mad/Sad/Glad: Emotion-focused
- Sailboat: Visual metaphor (wind=helps, anchor=holds back)
-
Gather Input Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.
-
Discuss and Prioritize Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.
What ships with it
5 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.
- 9d ago First seen · 96 lines · 61 tokens per session scan A 66f5c087ad20
iterate-retrospective is a skill published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 1,114 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
status-update-writer
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
stakeholder-update
Translate the same underlying project status into audience-appropriate versions (exec-brief, engineering-detail, customer-facing) without changing the underlying facts. Use when a PM needs to write a status update, especially when the same update needs to go to multiple different audiences. Pairs with…
scope-cut
Decision framework for what to cut when a spec, sprint, or launch is too big for the time or team available. Use whenever a PM says a scope needs to shrink, a deadline is fixed and the work isn't, or someone asks "what can we cut" or "what's the MVP version of this." Also trigger when reviewing a spec that feels…
escalation-judgment
Decision framework for whether a blocker, risk, or conflict is actually worth escalating to leadership versus resolving at the working level. Use when a PM is unsure whether to "loop in" a director/VP, when a team is stuck and someone suggests escalating, or when reviewing whether a past escalation was warranted. Also…
okrs
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at…
shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable…