Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/0p9b/TLDRnpx agentmods add skills/0p9b/tldr/tldr-updateWrote 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/skills/0p9b/tldr/tldr-update)<a href="https://agentmods.dev/skills/0p9b/tldr/tldr-update"><img src="https://agentmods.dev/badge/skills/0p9b/tldr/tldr-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/0p9b/tldr/tldr-update"><img src="https://agentmods.dev/badge/skills/0p9b/tldr/tldr-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00356 |
| Opus 5.5 | $0.00029 | $0.00142 |
| Sonnet 5.5 | $0.00015 | $0.00071 |
| Haiku 4.5 | $0.00007 | $0.00036 |
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 2mo 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
TLDR Update
When invoked, run the update CLI via Bash and report the result. Do not invent SHAs — quote the command output.
How to run
Pick the first that applies:
- Local checkout — if
bin/install.jsexists here:node bin/install.js update $ARGUMENTS tldron PATH:tldr update $ARGUMENTS- Fallback:
npx -y github:0p9b/TLDR -- update $ARGUMENTS
Useful flags
| Flag | Effect |
|---|---|
--check |
Report available update; do not apply |
--dry-run |
Show git + reinstall plan; write nothing |
--ref <tag|branch> |
Update to that ref (alias: --tag) |
--force |
Hard-reset local checkout to origin/<ref> if ff-only fails (never force-pushes) |
Report
Tell the user: before SHA, after SHA, source path, and what the installer reinstalled. Exit code 0 = success / already up to date; 1 = failure.
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.
- 2mo ago First seen · 43 lines · 73 tokens per session scan A dc8d7369a4d5
tldr-update is a skill published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 356 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
agent-initialization
Initialize or extend an Agent from a user requirement - write AGENTS.md, set identity metadata, and create, install or import Skills and hook packages (scripts the harness runs on every prompt, before tool calls, or after a task). For an Agent with an in-app workbench, pair with penguin-plugin; for a standalone…
computer-history
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw event streams.
co-mail-and-drive
Read and send mail from the user's own Gmail or Outlook account, safely stage Gmail draft attachments, send from the agent's own address, manage Outlook contacts and the Outlook calendar, and work with Google Drive files — with co gmail, co outlook, co email, and co gdrive. Use when the user asks about their inbox, an…
dashboard
Update the agent's Control Center. Use when the user says "update my Control Center", "update my dashboard", "redesign my home", or "/dashboard".
co-google
Route Google account work to Gmail, Drive, Calendar, and YouTube CLI commands using one locally saved login.
unlazy
Enforces completion discipline for substantial autonomous work by writing acceptance gates before execution, decomposing work with the Depth Tree, running approved checks, and re-verifying evidence before reporting. Use when an agent faces a long or multi-part task, work that has returned half-done, an exhaustive…