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/leanos-technologies/strategy-os/gap-computing-ledgernpx skills add LeanOS-Technologies/strategy-os --skill gap-computing-ledgergit 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-computing-ledger)<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/gap-computing-ledger"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/gap-computing-ledger.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 | $0.00046 | $0.01721 |
| Opus 5 | $0.00023 | $0.00860 |
| Sonnet 5 | $0.00009 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
gap-computing-ledger 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gap Ledger Computation
Compute the distance between desired state and current state for each hypothesis and proposal in the register. Produce scored, ranked gap records that drive prioritization.
Process
Step 1: Extract Desired and Current States [S]
For each hypothesis section (Problem, Segment, Unit Economics, Value Proposition) and each proposal section (Growth Architecture, Solution Design, GTM Plan):
- Read the Desired State block. List every condition under "SUPPORTED means."
- Read the Current State block. For each condition, record its fulfillment status: MET, PARTIAL, MISSING, or CONTRADICTED.
- If a section has no Desired State block, mark the entire section as having a gap of type EVIDENCE_STRENGTH with note "no desired state defined."
Gate: states_extracted: bool -- every register section has a desired/current pair or is flagged as missing.
- Pass: Step 2.
- Fail: flag missing sections and proceed with available data.
Step 2: Score Each Gap [R]
For each condition that is not MET, compute a gap record using these scales:
Confidence Gap (0-3):
| Current Confidence | Desired Confidence | Score |
|---|---|---|
| unvalidated | supported | 3 |
| researched | supported | 2 |
| supported but thin | supported (robust) | 1 |
| supported | supported | 0 |
Evidence Weakness (0-3):
| Evidence Profile | Score |
|---|---|
| Only T3 / assertion-heavy | 3 |
| Mostly T2 | 2 |
| Mixed T1/T2 but thin | 1 |
| Enough T1 for decision | 0 |
Pain Uncertainty (0-3):
| Pain Clarity | Score |
|---|---|
| Unclear whether pain is real or acute | 3 |
| Partially clear | 2 |
| Mostly clear | 1 |
| Clear | 0 |
Time Penalty (0-2):
| Deadline Status | Score |
|---|---|
| Exceeded | 2 |
| Due or near due | 1 |
| Within deadline | 0 |
Blast Radius Weight (1-3):
| Impact If Wrong | Weight |
|---|---|
| Strategy collapses | 3 |
| One major hypothesis must change | 2 |
| Local revision only | 1 |
Final Priority Score:
Final Priority = (Confidence Gap + Evidence Weakness + Pain Uncertainty + Time Penalty) x Blast Radius Weight
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.
- 4d ago First seen · 185 lines · 46 tokens per session scan A a6ac33c953b0
gap-computing-ledger is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,721 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-30.
Other skills, from other repositories
crewai
Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative…
context7-auto-research
Automatically fetch latest library/framework documentation for Claude Code via Context7 API.
deep-research-notebooklm
Deep research skill powered by NotebookLM MCP. Conducts structured multi-source research (market analysis, competitive intel, trend analysis, prospect research) using Google NotebookLM as the research engine, then delivers formatted briefs and optional studio artifacts (slides, audio podcasts, videos, infographics…
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…