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 Jessinra/Lorekeeper --skill postmortem-writinggit clone --depth 1 https://github.com/Jessinra/LorekeeperWrote 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/jessinra/lorekeeper/postmortem-writing)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/postmortem-writing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/postmortem-writing/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/jessinra/lorekeeper/postmortem-writing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/postmortem-writing.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.00030 | $0.01257 |
| Opus 5.5 | $0.00012 | $0.00503 |
| Sonnet 5.5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
postmortem-writing scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
How the incident was first noticed (user report, alert, dashboard). Include evidence commands (e.g. `ps aux`, `curl` checks). How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postmortem Writing
Use this skill when authoring or reviewing an incident report (IR) for the Lorekeeper project. Every incident must produce durable process improvements — not just a fix but encoding the lesson into review patterns and checklists.
When to Use
- A production incident occurs (P0/P1)
- A CI pipeline breaks on
main - A bug with systemic root cause (not a one-off typo)
- The fix changes architecture patterns, not just code
Mandatory Deliverables
Every IR MUST deliver all of:
| # | Deliverable | Location | Why |
|---|---|---|---|
| 1 | docs/incidents/IR-NNN-description.md |
Repo docs/incidents/ |
Permanent record |
| 2 | BLOCKER pattern(s) added to lorekeeper-code-reviewer |
.hermes/skills/lorekeeper-code-reviewer/SKILL.md |
Prevents same bug class passing review |
| 3 | Checklist items added to github-code-review-checklist |
Skills directory | Catches in general review too |
| 4 | Engineering docs (if the pattern needs explanation) | docs/engineering/ |
Reference for future readers |
| 5 | Action items tracked to completion | IR action items table | Closure |
IR Template
YAML Frontmatter
---
**Status:** [Resolved | In Progress | Monitoring]
**Severity:** [P0/P1/P2]
**Date:** YYYY-MM-DD
**Author:** [Name]
**Fix PR:** #[number]
---
Sections
1. Summary
One paragraph: what happened, why it was bad, what fixed it. Include the key insight in the first sentence.
2. Timeline
Table of events in chronological order: time + event. Include first symptom, investigation start, fix identified, fix merged, recovery confirmed.
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 · 152 lines · 30 tokens per session scan A a64b6d64ecd1
postmortem-writing is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,257 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, Select, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
keyboard-shortcuts
Reference for keyboard shortcut implementation, keybinding registration, shortcut parity with vim and other TUI tools, and the complete shortcut assignment table across all sidecar plugins. Use when adding or modifying keyboard shortcuts, checking shortcut assignments, resolving key conflicts, or assessing alignment…
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.