Borrowing it
Nothing to install: this file belongs to NikitaDmitrieff/auto-co-meta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NikitaDmitrieff/auto-co-meta/main/.claude/skills/premortem/SKILL.mdgit clone --depth 1 https://github.com/NikitaDmitrieff/auto-co-metaWrote 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/nikitadmitrieff/auto-co-meta/premortem)<a href="https://agentmods.dev/skills/nikitadmitrieff/auto-co-meta/premortem"><img src="https://agentmods.dev/badge/skills/nikitadmitrieff/auto-co-meta/premortem/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/nikitadmitrieff/auto-co-meta/premortem"><img src="https://agentmods.dev/badge/skills/nikitadmitrieff/auto-co-meta/premortem.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.00042 | $0.00521 |
| Opus 5 | $0.00021 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
premortem 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 9d 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.
This is a copy
100% identical to premortem — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Mortem Analysis
Imagine the plan has completely failed, then work backward to identify what went wrong and how to prevent it.
Instructions
Set the scene: "It's [timeframe] in the future. This initiative was a complete disaster. Looking back, what happened?"
Generate failure scenarios without filtering for likelihood—get everything on the table first, then prioritize.
Output Format
The Plan Summarize what's being attempted and the success criteria.
Time Jump "It's [X months] later. This has failed completely. The outcome: [describe the disaster vividly]."
What Went Wrong
Generate 8-12 plausible failure causes across categories:
| Category | Failure Mode | How It Played Out |
|---|---|---|
| Execution | [What failed] | [The story of how] |
| External | [What failed] | [The story of how] |
| People | [What failed] | [The story of how] |
| Technical | [What failed] | [The story of how] |
| Assumptions | [What failed] | [The story of how] |
Risk Prioritization
| Failure Mode | Likelihood | Impact | Priority |
|---|---|---|---|
| ... | High/Med/Low | High/Med/Low | 1-5 |
Top 3 Risks & Mitigations
For each top risk:
- Risk: [Description]
- Early Warning Signs: What would indicate this is happening?
- Prevention: How to reduce likelihood
- Mitigation: How to reduce impact if it occurs
- Owner: Who's responsible for watching this?
Pre-Mortem Insights What did this exercise reveal that wasn't obvious before?
Revised Confidence After this analysis, how confident are you in success? What would increase confidence?
Guidelines
- Be vivid and specific—"the database corrupted" not "something went wrong"
- Include uncomfortable possibilities (key person leaves, competitor moves, we were wrong)
- Don't filter for "that won't happen"—the point is to surface hidden concerns
- Assign real owners to mitigations
- Look for single points of failure
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.
- 9d ago First seen · 67 lines · 42 tokens per session scan A dd0537f15332
premortem is a skill published in the GitHub repository NikitaDmitrieff/auto-co-meta (43 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 521 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to premortem, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.