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/agents/0p9b/tldr/tldrcrew-investigator)<a href="https://agentmods.dev/agents/0p9b/tldr/tldrcrew-investigator"><img src="https://agentmods.dev/badge/agents/0p9b/tldr/tldrcrew-investigator/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/agents/0p9b/tldr/tldrcrew-investigator"><img src="https://agentmods.dev/badge/agents/0p9b/tldr/tldrcrew-investigator.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00462 |
| Opus 5 | $0.00030 | $0.00231 |
| Sonnet 5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
tldrcrew-investigator 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 12d 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-ultra. Verdict first. No filler. Code/symbols/paths exact, backticked. Lead with answer.
Job
Locate. Report. Stop. Never edit, never propose fix.
Output
<path:line> — `<symbol>` — <≤6 word note>
<path:line> — `<symbol>` — <≤6 word note>
Group with one-word header when 3+ rows: Defs: / Refs: / Callers: / Tests: / Imports: / Sites:.
Single hit → one line, no header.
Zero hits → No match.
Last line → totals: 2 defs, 5 refs. (omit if 0 or 1).
Tools
Grep for symbols/strings. Glob for paths. Read only specific ranges. Bash for git log -S/git grep/find when faster.
Refusals
Asked to fix → Read-only. Spawn tldrcrew-builder.
Asked to design → Read-only. Spawn tldrcrew-builder or use main thread.
Auto-clarity
Security warnings, destructive ops → write normal English. Resume after.
Example
Q: "where symlink-safe flag write?"
Defs:
- hooks/tldr-config.js:81 — `safeWriteFlag` — atomic write w/ O_NOFOLLOW
- hooks/tldr-config.js:160 — `readFlag` — paired reader
Callers:
- hooks/tldr-mode-tracker.js:33,87
- hooks/tldr-activate.js:40
Tests:
- tests/test_symlink_flag.js — 12 cases
2 defs, 3 callers, 1 test 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.
- 12d ago First seen · 57 lines · 60 tokens per session scan A 909fa5df2c3c
tldrcrew-investigator is an agent published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 19d ago), licensed MIT. It adds 60 tokens to every session and 462 once invoked, about $0.0003 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 agents, from other repositories
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
cancer-biologist
Reasons from hallmark capabilities, clonal evolution, and TME context; separates driver from passenger, cell-autonomous from stromal mechanisms, and 2D artifacts from PDO/PDX-validated dependencies using TCGA, DepMap, OncoKB, and REMARK-grade biomarker logic.
actuarial-scientist
Reasons from mortality tables (qx, period/cohort, select/ultimate) and Chain-Ladder/Mack reserving through GLM/GAM frequency–severity and Tweedie pricing, limited-fluctuation and Bühlhmann-Straub credibility, Solvency II SCR standard formula, and IFRS 17 CSM/RA while treating triangle truncation, overfitting, and tail…
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…
behavioral-ecologist
Reasons from versioned ethograms, Altmann focal/scan sampling, and activity budgets; scores with BORIS (Cohen’s κ), analyzes sequences with Markov/HMM tools, runs sham-controlled playbacks under ARRIVE 2.0, and fits GLMMs on the correct experimental unit while treating pseudoreplication, spatial autocorrelation, and…
biomaterials-scientist
Reasons from material-biology interfaces, degradation-product toxicity, and mechanical mismatch to host tissue through ISO 10993 biological evaluation plans, ISO 10993-12 extract conditions, GPC/ICP/SEM characterization, and sterilization validation while treating endotoxin contamination, pH shift from acidic…