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 Dragoon0x/usemindit --skill mindit-premortemgit clone --depth 1 https://github.com/Dragoon0x/useminditWrote 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/dragoon0x/usemindit/mindit-premortem)<a href="https://agentmods.dev/skills/dragoon0x/usemindit/mindit-premortem"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-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/dragoon0x/usemindit/mindit-premortem"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-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.00109 | $0.01408 |
| Opus 5.5 | $0.00044 | $0.00563 |
| Sonnet 5.5 | $0.00022 | $0.00282 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
mindit-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 2mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindit-premortem
The second of three meta skills. Run this when the question is "what could kill this."
What this skill does
Inverts the design review. Instead of asking "is this good," it assumes the design has already failed and asks "what made it fail." This is the pre-mortem technique applied to design decisions. It surfaces failure modes that confident teams miss because they are reviewing for confirmation rather than refutation.
The skill is adversarial by design. Its goal is not to talk the team out of shipping. Its goal is to make the team's confidence honest by stress-testing it.
When to run this
- The user is about to ship something they feel good about, and you want to stress-test that confidence.
- The user asks "what could go wrong," "what are the risks," "what am I missing."
- The user explicitly asks for a devil's-advocate read or for arguments against a design.
- A pre-launch checklist would benefit from one final adversarial pass.
- The user is making a high-stakes irreversible choice (default change, brand refresh, pricing change, schema migration).
How to analyze
-
State the imagined failure. Write one sentence: "It is three months after launch. The design has failed in a way that is now obvious. The team is doing a post-mortem."
-
Brainstorm failure scenarios. Generate at least eight distinct ways the design could have failed. Use the eight forces as prompts:
- It failed because users could not understand it (clarity).
- It failed because it broke the conventions of the rest of the product (continuity).
- It failed because it hit a constraint we did not see (constraint).
- It failed because of a side effect we did not predict (consequence).
- It failed because we built it for the wrong audience or context (context).
- It failed because it cost more to maintain than we budgeted (cost).
- It failed because our evidence was wrong (confidence).
- It failed because we could not recover when we noticed it was wrong (correctability).
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.
- 2mo ago First seen · 113 lines · 109 tokens per session scan A 9c33a56711fd
mindit-premortem is a skill published in the GitHub repository Dragoon0x/usemindit (2 stars, last pushed 6mo ago), licensed MIT. It adds 109 tokens to every session and 1,408 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-08-31.
mindit-premortem compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mindit-premortemDragoon0x/usemindit | Skill | 2 | 6mo ago | MIT | A | 109 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |