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 liqiongyu/lenny_skills_plus --skill post-mortems-retrospectivesgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/post-mortems-retrospectives)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/post-mortems-retrospectives"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/post-mortems-retrospectives/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/liqiongyu/lenny_skills_plus/post-mortems-retrospectives"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/post-mortems-retrospectives.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.00028 | $0.02159 |
| Opus 5.5 | $0.00011 | $0.00864 |
| Sonnet 5.5 | $0.00006 | $0.00432 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
post-mortems-retrospectives 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 2mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-mortems & Retrospectives
Scope
Covers
- Running blameless incident post-mortems and project/OKR retrospectives
- Turning "what happened?" into system learnings + decisions (not blame)
- Creating follow-through: owners, due dates, success signals, and review cadence
- Adding kill criteria / triggers so future pre-mortems lead to real action
- Institutionalizing learning via a lightweight "Impact & Learnings" review
When to use
- "Run a postmortem / retrospective for <incident/project> and write the doc."
- "We missed OKRs—lead a retro focused on learning and systemic blockers."
- "Create an after-action review with action items and owners."
- "Set up a weekly impact & learnings review so insights don't die in docs."
- "Do a pre-mortem and define kill criteria / pivot triggers."
When NOT to use
- The incident is still active (do incident response first; schedule the review after stabilization)
- The goal is to assign blame or evaluate an individual's performance (use HR/management processes)
- You need deep technical debugging without the right experts (this skill facilitates; it doesn't replace engineering investigation)
- You need to decide what problem to solve (use a problem-definition / discovery process first)
- You need to facilitate a meeting that is not a post-mortem or retrospective (use
running-effective-meetings) - You need to improve the shipping process itself, not review a past launch (use
shipping-products) - You need to change engineering culture or practices based on systemic patterns across retros (use
engineering-culture) - You need to plan for future risks and uncertainties rather than review past events (use
planning-under-uncertainty)
Inputs
Minimum required
- What are we reviewing? (incident / project / OKR period) + 1–2 sentence summary
- Time window and key dates (start/end; detection time; resolution time if incident)
- Desired outcome (learning, prevention, speed, quality, alignment)
- Participants/roles (facilitator, scribe, decision owner; key stakeholders)
- Evidence available (timeline notes, metrics, dashboards, tickets, docs)
- Constraints (privacy; what to anonymize; audience)
What ships with it
13 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.
- eval/eval_config.json 1.6 KB
- eval/SHOWCASE.md 6.2 KB
- eval/with_skill.md 26 KB
- eval/without_skill.md 13 KB
- README.md 1.2 KB
- references/CHECKLISTS.md 1.8 KB
- references/EXAMPLES.md 877 B
- references/INTAKE.md 2.2 KB
- references/RUBRIC.md 3.0 KB
- references/SOURCE_SUMMARY.md 2.3 KB
- references/TEMPLATES.md 3.3 KB
- references/WORKFLOW.md 4.2 KB
- skillpack.json 397 B
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.
- 2mo ago First seen · 134 lines · 28 tokens per session scan A bf300fccd18c
post-mortems-retrospectives is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (53 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,159 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-08-30.
post-mortems-retrospectives compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| post-mortems-retrospectivesliqiongyu/lenny_skills_plus | Skill | 53 | 5mo ago | Apache-2.0 | A | 28 | Claude Code, Codex |
| happiness-skillkangarooking/cangjie-skill | Skill | 12k | 1mo ago | MIT | A | 136 | Claude Code, Codex |
| setup-matt-pocock-skillsdevcxl/mattpocock-skills-zh | Skill | 530 | 3d ago | MIT | A | 43 | Claude Code, Codex |
| pixel-art-studioAnastasiyaW/codex-claude-code-config | Skill | 214 | yesterday | MIT | A | 349 | Claude Code |
| config-validatorjmagly/aiwg | Skill | 229 | yesterday | MIT | A | 15 | Claude Code, Codex |
| aiwg-regenerate-copilotjmagly/aiwg | Skill | 229 | yesterday | MIT | A | 25 | Claude Code, Codex |
| link-checkjmagly/aiwg | Skill | 229 | yesterday | MIT | A | 29 | Claude Code, Codex |