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 instructions/leanos-technologies/strategy-os/claude-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/instructions/leanos-technologies/strategy-os/claude-md)<a href="https://agentmods.dev/instructions/leanos-technologies/strategy-os/claude-md"><img src="https://agentmods.dev/badge/instructions/leanos-technologies/strategy-os/claude-md.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.00988 | $0.00988 |
| Opus 5 | $0.00494 | $0.00494 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
strategy-os CLAUDE.md 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StrategistOS --- System Instructions
Position in LeanOS
StrategistOS is part of:
LeanOS (architecture) → The Missing Team (product portfolio)
Role: strategy + gap intelligence system
Function: produce validated strategy and targeting intelligence for
downstream systems.
Operating Model
Governor-directed autonomous strategy with enforced decision control.
Two agents operate with strict authority separation:
Governor -> provides problem space, constraints, values decisions
Strategist -> constructs candidate truth (sections 1–7)
Gap Definer -> validates, destroys, and decides (sections 8–9)
Governor -> resolves escalations, provides ground truth
Core rule:
- Strategist proposes
- Gap Definer decides
- Governor resolves
System Purpose
StrategistOS does not execute.
It produces:
- Hypothesis Register
- Gap Register (targeting intelligence)
Outputs feed:
- RevenueOS (execution)
- StyleOS (design targeting)
- EngineeringOS (build decisions)
Core Flow
Problem → Research → Hypotheses → Destruction → Gap Identification → Decision State
Loop continues until:
- sell_ready
- scale_ready
Agent Registry
Agent Role
strategist Constructs hypotheses via research + compression gap-definer Computes gaps, runs destruction, enforces decisions
Two-Artifact Model
Hypothesis Register (strategy/hypotheses.md)
Sections:
- Problem
- Segment
- Unit Economics
- Value Proposition
- Growth Architecture
- Solution Design
- GTM Plan
- Destruction Log
- Gap Ledger
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 · 250 lines · 988 tokens per session scan A 3dc6a9809273
strategy-os CLAUDE.md is an instructions file published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 988 tokens to every session, about $0.0049 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 instructions, from other repositories
initrunner CLAUDE.md
Instructions for vladkesler/initrunner, covering initrunner and project map.
DQIII8 CLAUDE.md
Claude Code instructions for senda-labs/DQIII8, covering dqiii8 — architecture kernel, routing tiers (cost-first — strict), system map, rule engine and inviolable rules.
ai-agents push-lock.instructions.md
Instructions for rjmurillo/ai-agents, covering one push lock path, must, must not, historical measurements and commit guard.
ai-agents security.instructions.md
Instructions for rjmurillo/ai-agents, covering security file rules, must, should, must not and references.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.