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-commit)<a href="https://agentmods.dev/commands/0p9b/tldr/tldr-commit"><img src="https://agentmods.dev/badge/commands/0p9b/tldr/tldr-commit/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/commands/0p9b/tldr/tldr-commit"><img src="https://agentmods.dev/badge/commands/0p9b/tldr/tldr-commit.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.00020 | $0.00069 |
| Opus 5.5 | $0.00008 | $0.00028 |
| Sonnet 5.5 | $0.00004 | $0.00014 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
tldr-commit 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 1mo 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
Generate a TLDR commit message for the current staged changes. Conventional Commits format. Subject: ≤50 chars, imperative. Body only when why is not obvious. Why over what. No filler. Truth and utility only.
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.
- 1mo ago First seen · 6 lines · 20 tokens per session scan A 793c6af9d912
tldr-commit is a command published in the GitHub repository 0p9b/TLDR (23 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 69 once invoked, about $0.0001 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 commands, from other repositories
eg-precommit-review
Run the pre-commit independent-reviewer loop on the current branch's pending changes.
gpd:quick
Execute a quick research task with GPD guarantees (atomic commits, state tracking) but skip optional agents.
commit
Use the text the user typed after the command name as the request for this command.
cm
Stage working tree changes and create a Conventional Commit (no push).
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
apex-git-commit
Stage everything except agent-output/, infra/, and .github/skills/sensei/ (unless on feat/skills-sensei), auto-generate a conventional commit, push, then prompt to open or update a PR. CLI-only (git + gh).