Borrowing it
Nothing to install: this file belongs to LeanOS-Technologies/strategy-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LeanOS-Technologies/strategy-os/main/.claude/skills/gap-running-destruction/SKILL.mdgit clone --depth 1 https://github.com/LeanOS-Technologies/strategy-osWrote 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/leanos-technologies/strategy-os/gap-running-destruction)<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/gap-running-destruction"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/gap-running-destruction.svg" alt="Measured on agentmods" 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.00051 | $0.01788 |
| Opus 5 | $0.00026 | $0.00894 |
| Sonnet 5 | $0.00010 | $0.00358 |
| Haiku 4.5 | $0.00005 | $0.00179 |
Grade A, and why
gap-running-destruction 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 8d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Destruction Protocol
Execute adversarial analysis against the hypothesis register. The purpose is to find what is wrong, not to confirm what is right. Every mechanism must produce specific, actionable findings -- not generic warnings.
Process
Step 1: Extract Attack Surface [S]
From the register, extract:
- All hypothesis claims (Problem, Segment, Unit Economics, Value Proposition).
- All load-bearing assumptions (those marked LOAD-BEARING or with BLAST:HIGH).
- All evidence items with their tiers and provenance.
- Growth Architecture proposal and its required conditions.
- Solution Design proposal and its adequacy criteria.
- GTM Plan proposal and its success/kill criteria.
Gate: surface_extracted: bool -- at least one hypothesis claim and one assumption extracted. If register is empty, halt: nothing to destroy.
- Pass: Step 2.
- Fail: halt with message "register has no content to run destruction against."
Step 2: Run Pre-Mortem [K-grounded]
Grounded in: extracted claims, assumptions, evidence, market context from register.
Write a 12-month failure scenario:
- Identify the single most likely failure chain. Trace cause to effect through the register: which assumption fails first, what cascades, what kills the strategy.
- Name the dominant causal factor. "The strategy failed because..." must be specific (not "we didn't execute well" -- that is a non-answer).
- Identify what was missed or underweighted in the current register.
Quality criteria:
- The failure scenario must reference specific register content (hypothesis claims, assumption IDs, evidence gaps).
- The causal chain must have at least 2 links (trigger -> intermediate effect -> outcome).
- Generic failure modes ("ran out of money", "couldn't find product-market fit") are insufficient. Trace WHY through the register's own assumptions.
Fabrication boundary: Reason only over data present in the register and publicly known market dynamics. Do not invent customer reactions or market events.
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.
- 8d ago First seen · 170 lines · 51 tokens per session scan A a8587aeb2d2c
gap-running-destruction is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,788 once invoked, about $0.0003 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-30.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
gepetto
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.