recipe-post-mortem-setup

recipe-post-mortem-setup is a skill for Claude Code, Codex from fakoli/fakoli-plugins. It costs 28 tokens per session (485 once invoked), scanned A, original, MIT.

An incident follow-up workflow that creates a structured post-mortem document, schedules a review meeting, and notifies the team in Google Chat.

In plain words
What is it for?
Use it after an incident to record the summary, timeline, root cause, impact, action items, and lessons learned, then arrange a team review.
Why use it?
It brings the main follow-up tasks after an incident into one process instead of handling the document, meeting, and announcement separately.

Skill for Claude CodeCodex

Part of the gws plugin — 94 skills, 15 commands, 11 agents shipped together

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.

agentmods
npx agentmods add skills/fakoli/fakoli-plugins/recipe-post-mortem-setup
Any agent
npx skills add fakoli/fakoli-plugins --skill recipe-post-mortem-setup
Clone the repo
git clone --depth 1 https://github.com/fakoli/fakoli-plugins

Made for: Claude Code, Codex.

Or install gws, the plugin that ships this one along with the rest of its 94 skills, 15 commands, 11 agents.

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 recipe-post-mortem-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup.svg)](https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup)
Your own site
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.00485
Opus 5 $0.00014 $0.00243
Sonnet 5 $0.00006 $0.00097
Haiku 4.5 $0.00003 $0.00049

Measured yesterday against content hash c3e2c14bd3f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

recipe-post-mortem-setup 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 yesterday.

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.

plugins/gws/skills/recipe-post-mortem-setup/SKILL.md · 72 lines

What it actually says

Set Up Post-Mortem

Create a post-mortem document, schedule a review meeting, and notify the team — all in one workflow.

When to Use

Use this workflow after an incident when the user needs to set up the post-mortem process: create a structured document, schedule a review meeting, and notify the team.

Workflow

1. Gather incident details

Ask the user for:

  • Incident name (e.g., "API Outage 2026-03-14")
  • Team/attendees for the review meeting
  • Preferred review time
  • Chat space for the notification

2. Create the post-mortem document

gws docs +write \
  --title 'Post-Mortem: INCIDENT_NAME' \
  --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Impact\n\n## Action Items\n\n## Lessons Learned'

Capture the document ID.

3. Schedule the review meeting

gws calendar +insert \
  --summary 'Post-Mortem Review: INCIDENT_NAME' \
  --attendee [email protected] \
  --start 'REVIEW_TIME' \
  --end 'REVIEW_END_TIME' \
  --dry-run

Confirm, then execute.

4. Notify the team in Chat

gws chat +send \
  --space spaces/SPACE_ID \
  --text 'Post-mortem scheduled for INCIDENT_NAME. Doc: DOC_LINK | Review: MEETING_TIME'

5. Share the document

gws drive permissions create \
  --params '{"fileId": "DOC_ID"}' \
  --json '{"role": "writer", "type": "user", "emailAddress": "[email protected]"}'

Safety

  • Use --dry-run on the calendar event and chat message before executing
  • Confirm the attendee list and chat space with the user

Tips

  • Share the doc with writer access so the team can contribute
  • Include the doc link in the calendar event description
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. yesterday First seen · 72 lines · 28 tokens per session scan A c3e2c14bd3f1

Subscribe to this mod's changes

recipe-post-mortem-setup is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 28 tokens to every session and 485 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

docx

This skill should be activated when the user asks to create a Word document, report, memo, letter, proposal, whitepaper, or anything involving .docx output. Also triggers when the user says 'write a report', 'create a document', 'make a Word file', 'draft a proposal', 'generate a whitepaper', or mentions .docx.…

lukaskellerstein/claude-my-marketplace · 141 tokens

xlsx

This skill should be activated when the user asks to create, edit, read, or analyze Excel spreadsheet files (.xlsx, .xlsm, .csv, .tsv). Triggers for: building financial models, creating data tables, formatting spreadsheets, adding formulas, cleaning tabular data, converting between tabular formats. Also triggers when…

lukaskellerstein/claude-my-marketplace · 106 tokens

product-data-cleanup

Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.

AlpacaLabsLLC/skills-for-architects · 42 tokens

doc-html-slide

발표용 슬라이드 덱을 브라우저에서 바로 열리는 단일 파일·자체 완결형(self-contained) HTML로 만들어 드립니다. 인포그래픽(차트·다이어그램·KPI)은 한국어 숫자·라벨이 100% 정확한 인라인 SVG로 직접 렌더링하고, 실사 히어로·일러스트 이미지는 Higgsfield MCP 또는 codex(gpt-image-2)로 생성합니다. 필요 시 doc-pptx 체이닝으로 PowerPoint에서 편집 가능한 .pptx까지 병행 산출합니다. 다음과 같은 요청 시 사용하세요: "발표 슬라이드 HTML로 만들어줘" "키노트 덱 단일 HTML 파일로 렌더해줘"…

modu-ai/moai-cowork · 469 tokens

bib-coverage

Compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries. Use when the user asks to compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries.

flonat/flonat-research · 56 tokens

docx

Create, read, edit, or convert Microsoft Word documents while preserving professional document structure. Use when a .docx file is a primary input or requested output, including tracked changes, comments, images, headings, page furniture, or polished reports and letters. Not for PDFs, spreadsheets, Google Docs, or…

flonat/flonat-research · 68 tokens