publish-postmortem

publish-postmortem is a skill for Claude Code from ahmadulhoq/agentskel. It costs 56 tokens per session (78 once invoked), scanned A, original, MIT.

A workflow for writing a post-mortem after a production incident has been resolved. A post-mortem records what happened, why, and what should change afterward.

In plain words
What is it for?
Use it after a hotfix to publish the incident record, optionally create Jira action items, and link the findings to project lessons.
Why use it?
It turns an incident into documented lessons and trackable follow-up work instead of letting the causes be forgotten.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the agentskel plugin — 53 skills, 3 hooks shipped together

Good fit Use it after a hotfix to publish the incident record, optionally create…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ahmadulhoq/agentskel/publish-postmortem
Install

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.

Any agent
npx skills add ahmadulhoq/agentskel --skill publish-postmortem
Clone the repo
git clone --depth 1 https://github.com/ahmadulhoq/agentskel

Made for: Claude Code.

Or install agentskel, the plugin that ships this one along with the rest of its 53 skills, 3 hooks.

Wrote 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.

agentmods badge for publish-postmortem

README.md
[![agentmods](https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/publish-postmortem.svg)](https://agentmods.dev/skills/ahmadulhoq/agentskel/publish-postmortem)
Your own site
<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/publish-postmortem"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/publish-postmortem.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 78 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00078
Opus 5 $0.00028 $0.00039
Sonnet 5 $0.00011 $0.00016
Haiku 4.5 $0.00006 $0.00008

Measured 4d ago against content hash a0e9ddb2e7c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

publish-postmortem 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.

.claude/skills/publish-postmortem/SKILL.md · 6 lines

What it actually says

Read and follow the full workflow at .agents/workflows/publish-postmortem.md.

Changes

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.

  1. 4d ago First seen · 6 lines · 56 tokens per session scan A a0e9ddb2e7c4

Subscribe to this mod's changes

publish-postmortem is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 20d ago), licensed MIT. It adds 56 tokens to every session and 78 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-02.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens