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 Ingramradical235/anty-framework --skill failure-essencegit clone --depth 1 https://github.com/Ingramradical235/anty-frameworkWrote 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/ingramradical235/anty-framework/failure-essence)<a href="https://agentmods.dev/skills/ingramradical235/anty-framework/failure-essence"><img src="https://agentmods.dev/badge/skills/ingramradical235/anty-framework/failure-essence/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/ingramradical235/anty-framework/failure-essence"><img src="https://agentmods.dev/badge/skills/ingramradical235/anty-framework/failure-essence.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.00079 | $0.01392 |
| Opus 5 | $0.00039 | $0.00696 |
| Sonnet 5 | $0.00016 | $0.00278 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
failure-essence 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 10d 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 failure-essence — 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Failure Patterns (Essence of Failure)
When to Apply
- Creating or reviewing Strategy Kernels
- When Goals have multiple competing objectives
- When strategy language is vague or ambiguous
- When a project should potentially be stopped
- When assumptions underlying strategy need validation
Core Framework
1. Dual-Objective Trap Detection
When a Goal or Driver has two stated objectives, run a conflict stress test:
Goal: "Acquire 100 enterprise customers AND maintain 90% gross margin"
Conflict Stress Test:
"Under what resource/timing constraints do these conflict?"
-> Enterprise sales requires high-touch (high CAC)
-> 90% margin limits sales investment
-> Below $50K deal size, these are mutually exclusive
"DUAL-OBJECTIVE CONFLICT detected. Under resource constraints,
you cannot maximize both. Which is PRIMARY?"
-> User designates primary; other becomes subordinate with floor.
Applied to: Goal creation, Driver creation, Strategy Kernel formulation. Any time two objectives appear in the same scope.
Resolution: One objective is PRIMARY (maximized). The other becomes SUBORDINATE with a minimum acceptable floor (not zero, just not maximized).
2. Strategic Ambiguity Detection
When Strategy Kernel or User Rules contain terms that could be interpreted divergently, test for operationalizability:
Guiding Policy: "Focus on high-value customers"
Ambiguity Test:
"Could two people read 'high-value' and derive opposite actions?"
Interpretation A: "Enterprise, $100K+ deals"
Interpretation B: "High-NPS users who generate referrals"
-> DIVERGENT INTERPRETATION detected.
"Define 'high-value' operationally:
- What metric defines it?
- What threshold?
- What would PROVE this strategy is working?
- What would PROVE it is failing?"
Applied to: Guiding Policy terms, Driver titles, Action descriptions. Any abstract concept that drives resource allocation.
The test: Can two reasonable people read this and derive opposite actions? If yes, the term is dangerously ambiguous.
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.
- 10d ago First seen · 146 lines · 79 tokens per session scan A 9fc01a9506df
failure-essence is a skill published in the GitHub repository Ingramradical235/anty-framework (1 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 1,392 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to failure-essence, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
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.…
review-engine
5-question review framework (result, execution, plan, strategy, analysis), KPI propagation monitoring with 4-layer anomaly patterns, One-Way/Two-Way Door classification, withdrawal decision protocol, and assumption provenance auditing. Use during periodic reviews, buffer zone changes, or when evaluating why results…
anticipatory-selling
Auto-generate 5 sales support materials for pipeline Steps 5-7 — competitive comparison table, 3-year TCO analysis, internal proposal template, objection rebuttals, phased implementation timeline. Core principle is arming the buyer to sell internally. Use when deals reach Step 5+ or when win rates at Steps 5-7 are low.
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…
confidence
Contextual confidence calibration — DEFLATE for One-Way Doors and RED zones, PROTECT for Two-Way Doors and fundraising, "How does this work step by step?" depth testing, values-to-consequences redirect, unanimity as risk signal. From Knowledge Illusion — overconfidence is sometimes functional. Use when calibrating…