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 IkarusMK/AIcortex --skill blameless-postmortemgit clone --depth 1 https://github.com/IkarusMK/AIcortexWrote 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/ikarusmk/aicortex/blameless-postmortem)<a href="https://agentmods.dev/skills/ikarusmk/aicortex/blameless-postmortem"><img src="https://agentmods.dev/badge/skills/ikarusmk/aicortex/blameless-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.
<a href="https://agentmods.dev/skills/ikarusmk/aicortex/blameless-postmortem"><img src="https://agentmods.dev/badge/skills/ikarusmk/aicortex/blameless-postmortem.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00299 |
| Opus 5.5 | $0.00014 | $0.00120 |
| Sonnet 5.5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
blameless-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 1mo 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.
What it actually says
Blameless Postmortem
When to use
After any incident worth learning from (outage, data issue, security event).
Principle
Blame the system, not the person. People act reasonably given the information and tools they had. If a single human error caused an outage, the system let it.
Structure
- Summary — one paragraph: what broke, who was affected, how long.
- Impact — users/requests affected, duration, data integrity, money if any.
- Timeline — UTC timestamps: detection → diagnosis → mitigation → resolution.
- Root cause — the real underlying cause, not the trigger. Use "5 whys".
- What went well / what didn't — detection speed, tooling, comms.
- Action items — each with an owner and a due date; prefer systemic fixes (guardrails, alerts, tests) over "be more careful".
Smell tests
- A name appears as the "cause" → reframe to the systemic gap.
- Action items are vague ("improve monitoring") → make them concrete and owned.
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.
- 1mo ago First seen · 29 lines · 35 tokens per session scan A bdc3a8bfec0c
blameless-postmortem is a skill published in the GitHub repository IkarusMK/AIcortex (10 stars, last pushed 16d ago), licensed Apache-2.0. It adds 35 tokens to every session and 299 once invoked, about $0.0001 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-31.
Other skills, from other repositories
1panel-app-builder
Use when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories, icons, README files, and 1Panel validation.
eval
Measure retrieval quality — Hit@5, MRR, Precision@5 on a fixed fixture set, or Hit@5/MRR/nDCG@10 on your own corpus via the real-corpus benchmark. Regression tracking against a saved baseline, plain-English interpretation, and tuning pointers when numbers look off. Use after every ingest or config change.
ingest
Populate the gnosis-mcp knowledge base — from local files, git history, or a crawled website. Handles the full matrix of flags (--force, --prune, --wipe, --embed, --include-crawled) in one place.
setup
First-time setup wizard for Gnosis MCP. Install, init the database, ingest a docs folder, wire your editor — in that order.
status
Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.
tune
Find the chunk-size and retrieval config that maximizes quality on YOUR corpus. Sweeps chunk sizes, runs a golden-query set, reports nDCG / MRR / Hit@5. Use after first ingest or whenever your corpus changes shape significantly.