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-update)<a href="https://agentmods.dev/commands/0p9b/tldr/tldr-update"><img src="https://agentmods.dev/badge/commands/0p9b/tldr/tldr-update.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.00015 | $0.00186 |
| Opus 5 | $0.00008 | $0.00093 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
tldr-update 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 6d 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
Update TLDR to the latest release (or a named ref), then refresh installed agents.
How to run — pick the first that applies:
- If
bin/install.jsexists in the current repo (a TLDR checkout), run:node bin/install.js update $ARGUMENTS - Else if
tldris on PATH:tldr update $ARGUMENTS - Else:
npx -y github:0p9b/TLDR -- update $ARGUMENTS
Report the command output to the user: before SHA, after SHA, and what was reinstalled. Prefer --check first when the user only asked whether an update is available.
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.
- 6d ago First seen · 15 lines · 15 tokens per session scan A 3b88fd95a0e0
tldr-update is a command published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 186 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
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
gpd:update
Update GPD to latest version with changelog display.
reflect-skills
Run the local claude-reflect skill-discovery fallback and propose skill/rule changes without applying them.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.