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-compressgit 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.00018 | $0.00329 |
| Opus 5 | $0.00009 | $0.00164 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
lean-compress 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
Compress the memory file at "$ARGUMENTS" into a denser form that costs fewer input tokens on every future session, without losing any meaning.
Steps:
- First back up the original: copy "$ARGUMENTS" to "$ARGUMENTS.bak".
- Rewrite "$ARGUMENTS" in place, following these rules:
- Preserve byte for byte: every code block, inline code span, command, file path, URL, config key and value, and env var name. Never reword or reformat these.
- Compress only the prose around them. Drop filler, merge redundant lines, use terse fragments, remove restated context.
- Keep every distinct instruction, rule, fact, and preference. This is about cutting words, not information. If in doubt, keep it.
- Keep Laravel and PHP terms verbatim (Eloquent, Artisan, Blade, facades,
php artisan).
- Verify nothing technical was lost, and show me the output:
node "${CLAUDE_PLUGIN_ROOT}/bin/lean-compress.mjs" check "$ARGUMENTS.bak" "$ARGUMENTS" - If the verifier prints PRESERVATION: FAIL, restore from the .bak file and tell me exactly which item was lost. Do not keep a rewrite that failed the check.
- If it passes, report the size reduction from the verifier and remind me the original is saved at "$ARGUMENTS.bak".
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 · 19 lines · 18 tokens per session scan A 1840fe0ac68d
lean-compress is a command published in the GitHub repository ousid/lean (4 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 329 once invoked, about $0.0001 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 스킬을 실행합니다.