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 GeoffreyCoulaud/bgcpm --skill post-mortemgit clone --depth 1 https://github.com/GeoffreyCoulaud/bgcpmWrote 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/geoffreycoulaud/bgcpm/post-mortem)<a href="https://agentmods.dev/skills/geoffreycoulaud/bgcpm/post-mortem"><img src="https://agentmods.dev/badge/skills/geoffreycoulaud/bgcpm/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.1 | $0.00030 | $0.01598 |
| Opus 5 | $0.00015 | $0.00799 |
| Sonnet 5 | $0.00006 | $0.00320 |
| Haiku 4.5 | $0.00003 | $0.00160 |
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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Mortem
Guide the user through writing a blameless post-mortem by asking questions one at a time, depth-first. Extract knowledge from the conversation and formalize it into a structured markdown document. Adapt to the user's language from the first message.
When to Use
- After an incident has been resolved (technical, operational, organizational)
- When the team needs to document root causes and corrective actions
- For any incident type: outage, data loss, security event, process failure
Do NOT use for:
- Retrospectives or sprint reviews (different format and purpose)
- Ongoing incidents (resolve first, then document)
- Minor issues that need a bug report, not a post-mortem
Iron Rules
- One question at a time. Never bundle questions.
- Adapt to the user's language. Detect from first message, use throughout. All produced documents use the same language.
- No em-dashes, no emojis in any produced content.
- Factual and neutral tone. Never blame an individual. Focus on systems and processes.
- Mandatory review. Never finalize without the review sub-agent phase.
- No fluff in productions. Every element must add comprehension or structure. Remove empty sections and decorative diagrams. This does NOT apply to questioning: always confirm with the user, even when the answer seems obvious.
Interaction Model
Subjects below are a checklist, not sequential steps. Order is recommended, not imposed.
- Depth-first. Explore each subject fully before moving on. Dig into sub-topics as they emerge.
- Progress counter. Display "~N questions remaining" estimated from uncovered subjects. N can increase.
- On-the-fly corrections. Integrate corrections without formally returning to a previous subject.
- Natural conversation, structured document. The conversation can be messy. The final document is rigorous.
Subjects to Cover
Cover all subjects before production. Order is recommended, not imposed.
1. General context
- Who is writing? What incident? When? Who was involved? What system affected?
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 189 lines · 30 tokens per session scan A 285e2d690f44
post-mortem is a skill published in the GitHub repository GeoffreyCoulaud/bgcpm (4 stars, last pushed 5mo ago), licensed Unlicense. It adds 30 tokens to every session and 1,598 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
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…