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 | $0.00037 | $0.00999 |
| Sonnet 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 11d 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.
- 11d 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 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,997 once invoked, about $0.0004 per session on Opus 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
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
spec-herdr-review
Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…
gpmc
Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…
grok-session
Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
codex-session
Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…