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 agentmods add skills/marcozorn/agencykit/post-mortemnpx skills add MarcoZorn/agencykit --skill post-mortemgit clone --depth 1 https://github.com/MarcoZorn/agencykitWrote 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/marcozorn/agencykit/post-mortem)<a href="https://agentmods.dev/skills/marcozorn/agencykit/post-mortem"><img src="https://agentmods.dev/badge/skills/marcozorn/agencykit/post-mortem.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.02250 |
| Opus 5 | $0.00019 | $0.01125 |
| Sonnet 5 | $0.00008 | $0.00450 |
| Haiku 4.5 | $0.00004 | $0.00225 |
Grade A, and why
post-mortem 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 5d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Mortem
When to use this skill
English: "post-mortem", "retrospective", "project done", "lessons learned", "wrap-up", "close out the project".
Italiano: "post-mortem", "retrospettiva", "progetto chiuso", "lezioni apprese", "chiusura progetto".
What this skill does
Runs a tight retrospective on a finished project and turns it into learning the agency keeps. It separates what to keep doing from what to stop, digs one level past the symptom to the root cause, and commits to three concrete changes for next time. Then it appends a structured entry to LESSONS.md in the project root, so the lesson survives past the meeting nobody wrote down.
Inputs required
- Project name and a one-line description of what it was.
- Outcome — delivered on time / late, on budget / over, client happy / not.
- What the team felt went well and badly — gather a few honest points; if the user only gives one side, prompt for the other.
- Any hard numbers — hours vs estimate, revisions, margin if known.
The tone is blame-free. The goal is better systems, not a search for who to fault. If the input names a person as "the problem", reframe it as a process gap.
Output format
- WHAT WORKED — keep doing.
- WHAT DIDN'T — stop or fix.
- ROOT CAUSES — 1–2 per issue, one level past the symptom.
- THREE CHANGES — concrete actions for the next similar project.
- LESSONS.md ENTRY — a structured block appended to the project's
LESSONS.md.
Brand voice
If a BRAND.md file exists in this skill's folder (.claude/skills/post-mortem/BRAND.md) or in .claude/brand/BRAND.md (global fallback), read it before generating output and apply its tone, terminology, and examples to all text you produce. A skill-local BRAND.md overrides the global one; if neither exists, use a clean, professional default voice.
Instructions
1. What worked — name it so it repeats
List the things that genuinely helped: a process, a decision, a person's call, a tool. Be specific enough that it can be deliberately repeated. "Good communication" is not a lesson; "daily 5-minute standup kept the client's feedback from piling up" is.
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.
- 5d ago First seen · 186 lines · 38 tokens per session scan A 72f05af59d47
post-mortem is a skill published in the GitHub repository MarcoZorn/agencykit (6 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 2,250 once invoked, about $0.0002 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
silicon-steward
人类供奉调度官，把人类该提供之资源、反馈与执行动作压成清单与协议.
project-retrospective
Generate a LESSONS.md from a finished project: what worked, what didn't, what to reuse, what to retire — formatted for next-project carry-over.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
memory-continuity
Preserves cross-session continuity with deterministic MEMORY.md, index.md, and snapshot handoffs under .agentic/memories/.
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
git-worktree-workspaces
Sets up and uses Git worktrees for parallel task workspaces in the same repository clone, including safe cleanup of local worktrees. Invoked when the user asks to work on multiple branches at once, isolate tasks without extra clones, or create/remove worktrees.