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 rjmurillo/ai-agents --skill pre-mortemgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/pre-mortem)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/pre-mortem"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/pre-mortem/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/rjmurillo/ai-agents/pre-mortem"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/pre-mortem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.02680 |
| Opus 5.5 | $0.00039 | $0.01072 |
| Sonnet 5.5 | $0.00019 | $0.00536 |
| Haiku 4.5 | $0.00010 | $0.00268 |
Grade A, and why
pre-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 28d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Mortem Risk Identification
When this skill activates, you become a pre-mortem facilitator. Your role is to guide users through prospective hindsight analysis, helping them identify project risks by imagining failure has already occurred.
Triggers
Activate when the user:
Run a pre-mortem on...What could cause this project to fail?Identify project risks for...What could go wrong with...Pre-mortem analysis
Quick Reference
| Phase | Duration | Output |
|---|---|---|
| 1. Brief | 2-3 min | Project context documented |
| 2. Failure Announcement | 30 sec | Mindset shift established |
| 3. Independent Analysis | 3-5 min | Individual failure reasons |
| 4. Round-Robin Collection | 5-10 min | Consolidated failure list |
| 5. Review and Mitigate | 10-15 min | Risk inventory with mitigations |
When to Use
Use this skill when:
- Starting a new project or feature and want to identify risks upfront
- Team is overly optimistic and potential downsides need surfacing
- Stakeholders need to understand risk before committing resources
- After major scope changes to reassess risk landscape
Use threat-modeling instead when:
- Analyzing security threats specifically (STRIDE, attack trees)
- Need structured vulnerability assessment, not general project risk
Use decision-critic instead when:
- Challenging a specific decision, not brainstorming broad risks
Why Pre-Mortem Works
Research by Gary Klein demonstrates that prospective hindsight (imagining an event has already occurred) increases the ability to identify reasons for outcomes by 30%.
Key psychological benefits:
- Reduces "damn-the-torpedoes" attitude - Acknowledging failure is possible
- Creates psychological safety - Dissenters can voice concerns as analysis, not criticism
- Surfaces hidden knowledge - People share what they know but fear saying
- Catches blind spots early - Before commitment and sunk costs
What ships with it
4 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.
- 28d ago Changed · +5 lines c8617075df6c
- 1mo ago First seen · 333 lines · 97 tokens per session scan A 34343eb62711
pre-mortem is a skill published in the GitHub repository rjmurillo/ai-agents (49 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 2,680 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
install-gemini-code-review-action
Installs, configures, or upgrades Dazbo's PR code review & issue triage GitHub Action (gemini-review-action) in a target repository. Use when the user wants to set up, configure, or update automated AI code reviews, issue triaging, or Gemini model workflows for their GitHub repository.
review-deep
Review change vs spec, plan, code quality heuristics, and repo rules; append remediation phase if needed.
apply-review-feedback
Classify and apply accepted PR/MR review feedback.
review-remote
Review open PR/MR and publish findings.
phoenix-review
Review completed work against the Intent Contract's acceptance criteria using objective evidence, not opinion — re-run every check, confirm no regressions, inspect the tamper-evident trace, and surface only real issues (bugs, unmet criteria, regressions). Use before shipping, after a feature is built, or when the user…
azure-devops-automation
CI/CD pipelines, infrastructure as code, and deployment automation for Azure workloads.