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 commands/ousid/lean/lean-statsgit clone --depth 1 https://github.com/ousid/leanWhat 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.00009 | $0.00196 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
lean-stats 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 yesterday.
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.
What it actually says
Run the lean-stats tool and show me the output. Do not invent numbers.
Steps:
- Find my most recent Claude Code transcripts if I did not pass paths:
ls -t ~/.claude/projects/*/*.jsonl | head. - Run
node "${CLAUDE_PLUGIN_ROOT}/bin/lean-stats.mjs" $ARGUMENTS.report <session.jsonl>gives real output tokens plus the compressible prose ceiling for one session.diff <baseline.jsonl> <lean.jsonl>gives the measured saving between a lean off run and a lean on run of the SAME prompts.
- Print the raw tool output. If it says a value is approx or unmeasured, keep that label. Never round an estimate into a headline number.
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.
- yesterday First seen · 14 lines · 9 tokens per session scan A d9e64b3b6db6
lean-stats is a command published in the GitHub repository ousid/lean (4 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 196 once invoked, about $0.0000 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 commands, from other repositories
moyu-strict
Invoke the moyu:moyu-strict skill and follow it exactly.
moyu-en
Invoke the moyu:moyu-en skill and follow it exactly.
moyu-ja
Invoke the moyu:moyu-ja skill and follow it exactly.
moyu-lite
Invoke the moyu:moyu-lite skill and follow it exactly.
moyu
Invoke the moyu:moyu skill and follow it exactly.
moyu-ko
moyu-ko 스킬을 실행합니다.