agentmods.dev

incident-postmortem

incident-postmortem is a skill for Claude Code from logly/mureo. It costs 150 tokens per session (2,059 once invoked), scanned A, original, Apache-2.0.

A procedure for writing a postmortem after a rescue or incident. A postmortem reconstructs what happened, identifies root causes, and records ways to prevent a repeat.

In plain words
What is it for?
Reviewing timelines and account data, classifying causes, producing a postmortem, recording insights, and proposing preventive changes after incidents.
Why use it?
It turns an emergency response into documented lessons and safeguards, without changing advertising campaigns or budgets.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is PREREQUISITE: Read `../_mureo-shared/SKILL.md` for auth, security rules, output format, and **Tool Selection** (Read/Write on Code, `mureo_strategy_*` / `mureo_.

Part of the mureo plugin — 27 skills, 1 MCP server shipped together

not rated 51repo +1 changed today A scan SkillSpector: pass 150 tokens original Apache-2.0

Good fit Reviewing timelines and account data, classifying causes, producing a postmortem, recording insights, and proposing preventive changes after incidents.

Compare 6 skills from other repositories ↓
View source ↗ logly/mureo mureo.io
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/logly/mureo
agentmods
npx agentmods add skills/logly/mureo/incident-postmortem

Made for: Claude Code.

Or install mureo, the plugin that ships this one along with the rest of its 27 skills, 1 MCP server.

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 incident-postmortem

README.md
[![agentmods](https://agentmods.dev/badge/skills/logly/mureo/incident-postmortem/github.svg)](https://agentmods.dev/skills/logly/mureo/incident-postmortem)
Your own site
<a href="https://agentmods.dev/skills/logly/mureo/incident-postmortem"><img src="https://agentmods.dev/badge/skills/logly/mureo/incident-postmortem/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.

agentmods 80×15 button for incident-postmortem

Your own site · 80×15
<a href="https://agentmods.dev/skills/logly/mureo/incident-postmortem"><img src="https://agentmods.dev/badge/skills/logly/mureo/incident-postmortem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,059 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00150 $0.02059
Opus 5.5 $0.00060 $0.00824
Sonnet 5.5 $0.00030 $0.00412
Haiku 4.5 $0.00015 $0.00206

Measured today against content hash b75f83766700, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

incident-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 today.

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.

mureo/_data/skills/incident-postmortem/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Incident Postmortem

PREREQUISITE: Read ../_mureo-shared/SKILL.md for auth, security rules, output format, and Tool Selection (Read/Write on Code, mureo_strategy_* / mureo_state_* MCP on Desktop / Cowork).

After the fire is out, learn from it. A rescue that is never reflected on repeats: the same root cause resurfaces, the same scramble happens, and nothing in the account got more resilient. This skill reconstructs what happened, finds the controllable cause, and converts the episode into durable know-how and guardrails.

This skill makes NO ad-platform writes — it changes no campaigns, ads, budgets, bids, or targeting. It only reads platform and state data, writes a postmortem document, appends the postmortem to action_log, saves insights via /learn, and — with explicit approval — edits STRATEGY.md ## Guardrails. Say this up front to the operator so they know nothing in the ad accounts moves during this review.

Prerequisites

  • STRATEGY.md and STATE.json must exist (run the onboard skill first)

Steps

Before you start: Run the Diagnostic preamble from ../_mureo-shared/SKILL.md — load learning insights (mureo_learning_insights_get) and consult advisors (mureo_consult_advisor) before drawing conclusions.

  1. Establish today: call mureo_state_get first, on every host (including Claude Code, where you would otherwise Read the file) and take server_now from its response — ISO 8601 with UTC offset, e.g. 2026-07-28T10:12:33+09:00. Its date is the only source of the current date for this run: the scan window in step 1, the detection lag in step 2, and every "has this action's observation_due window closed?" judgement are measured from it. Do not shell out (this skill must run in Bash-less headless hosts). The action_log timestamps and last_synced_at you reconstruct the timeline from are history — that is exactly what makes them useful here, and exactly why they are never "now". Never write server_now into STATE.json: it is a response field, and a persisted copy becomes tomorrow's stale "today".

Read the full file on GitHub · 56 lines

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. today Changed b75f83766700
  2. 2d ago Changed 34ed43998806
  3. 4d ago Changed 39389cbb05c1
  4. 6d ago Changed 3e14fba9d8df
  5. 7d ago Changed 1e069c6c67fe
  6. 23d ago Changed 9834b48496ce
  7. 25d ago Changed 2b3c1dda5a9a
  8. 27d ago Changed b4e31822425a
  9. 29d ago Changed 7e4c446d966a
  10. 1mo ago First seen · 56 lines · 150 tokens per session scan A 6618b4f672e7

Subscribe to this mod's changes

incident-postmortem is a skill published in the GitHub repository logly/mureo (51 stars, last pushed today), licensed Apache-2.0. It adds 150 tokens to every session and 2,059 once invoked, about $0.0006 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.

DebuggingWriting and docsadvertisingai-agentscligoogle-adsmarketingmcp
Related

Other skills, from other repositories

adspirer-ads-agent

Adspirer — AI-powered advertising and performance marketing agent. Manage Google Ads, Meta Ads (Facebook & Instagram), LinkedIn Ads, and TikTok Ads via natural language. 100+ tools for paid media campaign creation, live performance analysis, PPC keyword research with real CPC data, budget optimization, ad creative…

LeoYeAI/openclaw-master-skills · 141 tokens

adcp-advertising

Automate advertising campaigns with AI. Create ads, buy media, manage ad budgets, discover ad inventory, run display ads, video ads, CTV campaigns, and optimize ad performance. Perfect for marketing automation, programmatic advertising, media buying, ad management, campaign optimization, creative management, and…

LeoYeAI/openclaw-master-skills · 103 tokens

google-ads-manager

Google Ads campaign management - campaign setup, keyword research, bid optimization, and performance reporting.

claude-office-skills/skills · 22 tokens

ads-copywriter

Multi-platform ad copy generation for Google Ads, Meta/Facebook, TikTok, LinkedIn with A/B testing variants.

claude-office-skills/skills · 27 tokens

adspirer-ads-agent

Adspirer — AI-powered advertising and performance marketing agent. Manage Google Ads, Meta Ads (Facebook & Instagram), LinkedIn Ads, and TikTok Ads via natural language. 400+ tools for paid media campaign creation, live performance analysis, PPC keyword research with real CPC data, budget optimization, ad creative…

amekala/ads-mcp · 187 tokens

adcp-advertising

Automate advertising campaigns with AI. Create ads, buy media, manage ad budgets, discover ad inventory, run display ads, video ads, CTV campaigns, and optimize ad performance. Perfect for marketing automation, programmatic advertising, media buying, ad management, campaign optimization, creative management, and…

LeoYeAI/openclaw-master-skills · 103 tokens