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 gemini-cli-extensions/sre --skill postmortem-generatorgit clone --depth 1 https://github.com/gemini-cli-extensions/sreWrote 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/gemini-cli-extensions/sre/postmortem-generator)<a href="https://agentmods.dev/skills/gemini-cli-extensions/sre/postmortem-generator"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/postmortem-generator/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/gemini-cli-extensions/sre/postmortem-generator"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/postmortem-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 104 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
- medium Privilege Escalation · line 111 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00042 | $0.02501 |
| Opus 5.5 | $0.00017 | $0.01000 |
| Sonnet 5.5 | $0.00008 | $0.00500 |
| Haiku 4.5 | $0.00004 | $0.00250 |
Grade B, and why
postmortem-generator scanned grade B with 1 finding 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
* `HH:MM:SS`: ricc@ typed `sudo halt` (chubby fingers) <== <span style="color:red">Start of Incident</span> How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert PostMortem tech Writer, with deep SRE and Incident Management experience.
Your goal is to:
- ensure PoMo information is ready (see prerequisites).
- create a postmortem document, using the template below.
- ensure the document is clear, concise, and follows best practices for postmortem writing.
- ensure the document is in markdown format.
This has two complications: timeline and action items.
Prerequisites
Ensure you're able to fetch relevant data about the incident. This is not part of this tool, so it should be done by other tools or by users.
- Ensure that investigation is DONE before starting the PostMortem work. Just ensure the timeline CSV is built during the investigation.
- Feel free to abort if user is unable to provide tools or content for you to build the PM.
- When starting the PM, you should have all the right timeline info, a root cause, and a good understanding of what happens.
- Every incident should have a unique id, based on the Incident Management tooling you're using:
- Google IRM:
i_1234567890,omg/12345, .. - ServiceNow:
INC123456 - JIRA:
PROD-1234 - PagerDuty:
P123456or incident URL - ZenDesk:
#1234567 - ...
- Google IRM:
Execution order
To work correctly, you need to follow a simple, deterministic algorithm:
- Create a folder, like "out/postmortem-<unique_incident_id>/", within the context of the investigation folder. If it exists, try to understand what's already been done ;)
- Create a file "postmortem-<unique_incident_id>/PLAN.md", with a number of checkboxes for the steps you need to execute.
This ensures that you'll be able to resume your work if interrupted and makes your finite-state automaton process more transparent. Note: if unique_incident_id is missing, use
YYYYMMDDinstead. From now on, you're going to interact with the PLAN.md to pick up the next job and mark when done. You will concentrate on various phases: INVESTIGATION, POSTMORTEM DRAFTING, TIMELINE, ACTION ITEMS, POSTMORTEM FINALIZATION. - Create a file "postmortem-<unique_incident_id>/postmortem-base.md", copying from the template below.
- Create a file "postmortem-<unique_incident_id>/timeline.csv", with the additional context below.
- Start your investigation, and keep adding relevant events to the
timeline.csvfile. This might require multiple iterations. Consider using MCP tools from your Incident Management system or internal tools to fetch relevant data about the incident. - When the investigation is done, and the timeline is complete, generate the final postmortem document by merging the postmortem-base.md with the
timeline.csvfile into "postmortem-<unique_incident_id>/postmortem-final.md" - The final postmortem document should have a table for the timeline, and a table for the action items, but the action items bug_ids should be empty for now.
- Finally start filing bugs as described below, and update the
postmortem-final.mdfile with the action items. - Finalize the PM and ask user to review. Finally propose to create a new doc with this content in Google Docs and share with intended users for review. This might require Workspace extension to generate a Google Doc from MD.
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.
- 9d ago Changed · -4 tokens per session ace88194806c
- 1mo ago First seen · 225 lines · 46 tokens per session scan B 8b73027981d1
postmortem-generator is a skill published in the GitHub repository gemini-cli-extensions/sre (84 stars, last pushed 7d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,501 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…