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/0p9b/tldr/tldr-initgit 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-init)<a href="https://agentmods.dev/commands/0p9b/tldr/tldr-init"><img src="https://agentmods.dev/badge/commands/0p9b/tldr/tldr-init.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 | $0.00016 | $0.00210 |
| Opus 5 | $0.00008 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade C, and why
tldr-init scanned grade C with 2 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 5d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
2. Otherwise download and run the standalone script (it is self-contained and supports stdin execution): `curl -fsSL https://raw.githubusercontent.com/0p9b/TLDR/main/src/tools/tldr-init.js | node - $ARGUMENTS` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Otherwise download and run the standalone script (it is self-contained and supports stdin execution): `curl -fsSL https://raw.githubusercontent.com/0p9b/TLDR/main/src/tools/tldr-init.js | node - $ARGUMENTS` What it actually says
Write the per-repo TLDR rule files (Cursor, Windsurf, Cline, Copilot, opencode, AGENTS.md) into the current repo, then report the result.
How to run the init script — pick the first that applies:
- If
src/tools/tldr-init.jsexists in the current repo (you are inside a TLDR checkout), run:node src/tools/tldr-init.js $ARGUMENTS - Otherwise download and run the standalone script (it is self-contained and supports stdin execution):
curl -fsSL https://raw.githubusercontent.com/0p9b/TLDR/main/src/tools/tldr-init.js | node - $ARGUMENTS
Use --dry-run first if the user did not pass --force, so we never silently overwrite an existing rule file.
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.
- 5d ago First seen · 14 lines · 16 tokens per session scan C 02e79734247f
tldr-init is a command published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 210 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
specify
Create or update the feature specification from a natural language feature description.