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 runxhq/runx --skill postmortem-draftgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/postmortem-draft)<a href="https://agentmods.dev/skills/runxhq/runx/postmortem-draft"><img src="https://agentmods.dev/badge/skills/runxhq/runx/postmortem-draft/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/runxhq/runx/postmortem-draft"><img src="https://agentmods.dev/badge/skills/runxhq/runx/postmortem-draft.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.00045 | $0.00590 |
| Opus 5.5 | $0.00018 | $0.00236 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
postmortem-draft 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postmortem Draft
Produce a postmortem that never pretends unknowns are facts. The supplied incident fragments are the only evidence; the drafting agent separates what happened from what is suspected, and deterministic code verifies every claimed fact against the fragments. Publication is a gated proposal, never an effect of this skill.
Procedure
- Native
data.digestbinds the exact fragment set. - The drafting agent assembles a summary, an evidence-cited timeline, a root
cause with a status of
known,suspected, orunknown, open unknowns, and owned action items. - Deterministic enforcement checks every timeline entry and any non-unknown root cause: the cited fragment must exist and the quote must appear verbatim in that fragment's text. An invented citation refuses the whole run. Action items must carry an action and an owner.
- The verdict separates completeness from honesty: a fully cited postmortem
with a supported root cause and no open unknowns is
publishableand carries a publish proposal gated on a human approver throughmessage-send; a grounded but incomplete one sealsneeds_more_evidenceand publishes nothing.
To build the fragment set from live systems, compose web-fetch or store
reads upstream; the digest binds whatever evidence was supplied.
Running the incident belongs to its operator; this skill explains it afterward.
Output
postmortem (runx.postmortem.v1) carries decision (publishable,
needs_more_evidence, refused), summary, the cited timeline,
root_cause, unknowns, action_items, the gated publish_proposal or
null, validation, and the fragments digest. publish_performed is always
false.
Inputs are incident_ref and incident_fragments.
Agent task contracts
postmortem-draft-draft
Read incident_ref and incident_fragments from step inputs. Return
postmortem_draft with summary, timeline entries (each entry,
fragment_id, quote), root_cause (status, and for known or suspected a
statement, fragment_id, and quote), unknowns, and action_items
(each action, owner). Quote fragments verbatim, mark anything the
fragments do not support as unknown rather than asserting it, and never
invent fragments, quotes, owners, or deadlines.
What ships with it
7 files 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.
- 5d ago First seen · 55 lines · 45 tokens per session scan A acbb9258c2ef
postmortem-draft is a skill published in the GitHub repository runxhq/runx (104 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 590 once invoked, about $0.0002 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-10-18.
Other skills, from other repositories
rust-check
Run cargo check on the current Rust project to find compile errors.
openrig-skills
Use when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent…
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
developing-openrig
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not…