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 daddia/claude-for-strategy --skill pre-mortem-and-red-teamgit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/pre-mortem-and-red-team)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/pre-mortem-and-red-team"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/pre-mortem-and-red-team/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/daddia/claude-for-strategy/pre-mortem-and-red-team"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/pre-mortem-and-red-team.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.00074 | $0.01997 |
| Opus 5.5 | $0.00030 | $0.00799 |
| Sonnet 5.5 | $0.00015 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00200 |
Grade A, and why
pre-mortem-and-red-team 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Mortem and Red Team
When to use
Stress-test a recommendation, deal, or program before commitment — structured pre-mortem (assume failure, work backward), dis-confirming evidence hunt, devil's-advocate pass, and decision-quality score.
Use after analysis is drafted (business-case, evaluate-strategic-option, map-competitive-landscape) and before board, IC, or sponsor sign-off.
What this skill does not do
- Does not veto decisions — surfaces failure modes and evidence gaps; strategist decides proceed / pivot / stop.
- Does not replace legal, compliance, or security review — flags when those lanes are needed.
- Does not invent dis-confirming data — names searches and witnesses needed; tags model knowledge
[verify].
Preconditions
| Input | If missing |
|---|---|
| The recommendation or option under test | Ask — cannot pre-mortem without a stated bet |
| Decision audience and stakes | Ask once; calibrates depth |
| Supporting analysis artifact | Proceed from user summary; flag thin evidence |
Provisional mode
Thin input: run abbreviated pre-mortem on stated recommendation only; confidence structured first pass; list evidence needed for full red-team.
Trust spine
- Confidence bands (
option-evaluation):- High: Dis-confirming search run; devil's-advocate challenges tied to evidence; decision-quality score with explicit kill triggers.
- Medium: Pre-mortem complete; some dis-confirming paths unexplored — listed.
- Low: Recommendation paraphrase only — scaffold, not clearance.
- Strategic advice vs. support (mandatory): Surfaces challenges; does not silently pick stop/go —
[review]on proceed recommendation. - Accountability gap: Decision-quality score forces engagement; no "looks fine" conclusion without scored dimensions.
- Per
../../references/trust-conventions.mdfor GATE before external distribution.
Assumption audit
| Assumption | Status | If wrong, what breaks |
|---|---|---|
| Success conditions are explicit | [stated / implied / missing] | Pre-mortem targets wrong failure |
| Key dependencies named | [complete / partial / unknown] | Blind spots in failure tree |
| Dissenting stakeholders identified | [named / unknown] | Devil's advocate too friendly |
| Evidence for headline claim | [sourced / partial / narrative only] | Red team argues past the analysis |
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 · 192 lines · 74 tokens per session scan A 1fd747be41c6
pre-mortem-and-red-team is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,997 once invoked, about $0.0003 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.
Other skills, from other repositories
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…
to-pr
Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.