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 agentmods add skills/voxtechnologies/anty-framework/pre-mortemnpx skills add VoxTechnologies/anty-framework --skill pre-mortemgit clone --depth 1 https://github.com/VoxTechnologies/anty-frameworkWhat 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 | $0.00042 | $0.01256 |
| Opus 5 | $0.00021 | $0.00628 |
| Sonnet 5 | $0.00008 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00126 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pre-mortem — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Mortem & Scenario Planning
When to Apply
- Before finalizing any Strategy Kernel
- When planning a major initiative or Goal
- When buffer enters YELLOW zone (validate contingencies)
- When the founder is overly optimistic about a single plan
- Quarterly strategy reviews
Core Framework
Pre-Mortem (5-Step Process)
- Assume total failure: "It is 6 months from now. This strategy has completely failed. Why?"
- Enumerate causes: List 3-5 specific, concrete failure scenarios (not vague risks)
- For each cause, define:
- Prevention measure (what to do now)
- Plan B (what to do if it happens)
- Early warning KPI (what to watch)
- Trigger threshold (when to act)
- Rank by likelihood x impact
- Embed triggers into the monitoring system so Plan B activates automatically
Failure cause: "LinkedIn organic saturated — ICP exhausted in target segment"
Prevention: Track unique ICP accounts remaining; alert at <500
Plan B: Pivot to content-first -> community -> warm intro strategy
Early warning KPI: new connection acceptance rate declining
Trigger: acceptance rate < 15% for 2 consecutive weeks
Scenario Planning (4 Scenarios with Auto-Triggers)
Define quantitative trigger points for each scenario. When thresholds are hit, Plan B activates AUTOMATICALLY — removing human judgment to prevent bias (loss aversion, sunk cost).
| Scenario | Condition | Response |
|---|---|---|
| OPTIMISTIC | Exceeds target by 20%+ | Continue scaling. Increase targets. |
| BASE | 80-120% of target | Maintain strategy. Increase effort on constraint Driver. |
| PESSIMISTIC | 40-80% of target + buffer RED + growth <3%/week for 3 weeks | Auto-activate Plan B: pivot channel, reposition ICP, adjust pricing |
| CATASTROPHIC | <40% of target + buffer >90% + negative growth for 2 weeks | Full strategy reset: rebuild Strategy Kernel from scratch |
Future State Narrative (PR/FAQ)
Before executing any major initiative, write success AS IF it already happened:
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.
- 2d ago First seen · 121 lines · 42 tokens per session scan A 56c48d2fbff5
pre-mortem is a skill published in the GitHub repository VoxTechnologies/anty-framework (6 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,256 once invoked, about $0.0002 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
choice-architecture
Nudge-based choice architecture for 3-option selection UI — smart default vs active choice, outcome mapping, channel factors, RECAP, operational transparency with source attribution, post-decision reinforcement, error-forgiving undo, peak-end session design, user contribution acknowledgment. Use when presenting…
culture-map
Erin Meyer's Culture Map with 8 dimensions, 5 launch presets (US, JP, DE, UK, FR), Layer A agent-user adaptation, Layer B content-target market adaptation, and anti-sycophancy tone calibration per culture. Use when adapting communication style to the founder's culture, localizing content for target markets, or when…
failure-essence
4 strategic failure patterns from Essence of Failure — dual-objective trap (conflict stress test), strategic ambiguity (operationalizability test), withdrawal decision protocol (pre-committed stop conditions, re-present biweekly), assumption provenance auditing (source, verification, load-bearing flag, sample size).…
pipeline
Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter…
plan-b
Plan B framework — 6 environmental forces monitoring, pre-mortem 5-step process, scenario planning with auto-trigger points, Devil's Advocate on every proposal, 100-day gate reviews, S-curve awareness, 5 hurdles to Plan B execution, boomerang prevention. Use when preparing contingencies, monitoring environmental…
quest-interview
QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test.…