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.
git clone --depth 1 https://github.com/0p9b/TLDRWrote 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/commands/0p9b/tldr/tldr-help)<a href="https://agentmods.dev/commands/0p9b/tldr/tldr-help"><img src="https://agentmods.dev/badge/commands/0p9b/tldr/tldr-help.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.00013 | $0.00191 |
| Opus 5 | $0.00006 | $0.00096 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
tldr-help 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 7d 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.
What it actually says
Show the TLDR quick-reference card.
| Command | What |
|---|---|
/tldr |
Activate at default level (full) |
/tldr lite |
Light compression — ~30% tokens dropped |
/tldr ultra |
Maximum compression |
/tldr wenyan[-lite|-ultra] |
Classical Chinese compression |
/tldr off |
Deactivate |
/tldr-commit |
Terse commit message |
/tldr-review |
One-line review findings |
/tldr-compress <file> |
Compress a Markdown file |
/tldr-stats |
Lifetime token-savings |
Natural language also works: "turn on TLDR", "stop tldr", "normal mode".
Code, commits, security warnings: TLDR drops out automatically.
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.
- 7d ago First seen · 21 lines · 13 tokens per session scan A fe0779564f03
tldr-help is a command published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 191 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-30.
Other commands, from other repositories
feedback
Review, capture, and promote curated user-feedback candidates detected from session hooks.
inventory
Track wiki-adjacent things the user cares about: items, Ideas, ingest candidates, entities, corpora, open questions, tasks, and other durable inventory records.
gpd:settings
Configure autonomy, unattended execution budgets, runtime permission sync, workflow preset bundles, model-cost posture, runtime-specific tier model overrides, review cadence, and git preferences.
gpd:update
Update GPD to latest version with changelog display.
hep-connect.body
A command for connecting Telegram chats to an Agentlas agent, team, group, or organisation chart.
honest-status
Give an honest status of the current work — what was actually done, hoped-for vs. real result, and what was missed or remains unproven. The plumb line for your own progress. Use when the user asks "what did you do / how well did it go / what's the status", before continuing a long task, or whenever a claim of…