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 skills add qurore/speckit-tldr --skill tldr-deletegit clone --depth 1 https://github.com/qurore/speckit-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/skills/qurore/speckit-tldr/tldr-delete)<a href="https://agentmods.dev/skills/qurore/speckit-tldr/tldr-delete"><img src="https://agentmods.dev/badge/skills/qurore/speckit-tldr/tldr-delete/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/qurore/speckit-tldr/tldr-delete"><img src="https://agentmods.dev/badge/skills/qurore/speckit-tldr/tldr-delete.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.00123 | $0.01387 |
| Opus 5 | $0.00062 | $0.00694 |
| Sonnet 5 | $0.00025 | $0.00277 |
| Haiku 4.5 | $0.00012 | $0.00139 |
Grade C, and why
tldr-delete scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`rm -rf` a feature directory. How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit TLDR — delete generated output
The companion to the tldr skill. It cleans up the review artifacts that tldr
writes (*.tldr.html / *.tldr.md, under specs/<feature>/tldr/) so they do not
get committed in a pull request. The TLDRs are a local reviewing aid, not
something the PR itself should carry.
Core safety rules (read first)
- Only ever delete generated TLDR artifacts. In scope: files matching
*.tldr.htmland*.tldr.md, plus atldr/directory once it is empty. NEVER deletespec.md,plan.md,research.md,tasks.md,contracts/, or anything else — those are the source, not the output. - Discover → list → confirm → delete. Always show the exact list of paths you are about to remove and get the user's confirmation first, unless the user already gave an explicit go-ahead ("yes, delete them", "force", "no prompt").
- Never delete with a wildcard. Expand the glob to explicit paths first, show
those paths, then remove exactly those. Do not pass
*torm, and neverrm -rfa feature directory. - Respect git. A file that is already committed must be removed with
git rm(so the deletion is staged and actually leaves the PR); a file that is untracked is simply removed from disk.
Step 1 — Resolve scope
Parse the argument ($ARGUMENTS) and also honor natural language:
spec→ onlyspec.tldr.html/spec.tldr.md.plan→ onlyplan.tldr.html/plan.tldr.md.bothor no argument → both the spec and plan TLDRs for the target feature.all→ every*.tldr.html/*.tldr.mdunderspecs/across the repo.- A path (a file, or a
specs/<feature>/dir) → operate on exactly that.
Find the target feature directory the same way the tldr skill does: if the user
names a feature, glob specs/*<feature>*/; otherwise infer from the current
PR/branch (the changed specs/<feature>/ files); if still ambiguous, list the
candidates under specs/ and ask. For all, skip feature resolution and search
the whole repo.
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.
- 11d ago First seen · 125 lines · 123 tokens per session scan C 86be5dc1790a
tldr-delete is a skill published in the GitHub repository qurore/speckit-tldr (3 stars, last pushed 2mo ago), licensed MIT. It adds 123 tokens to every session and 1,387 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
cad-reviewer-contract
Internal role contract, preloaded into every cad-reviewer rung agent. Not a user command.
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
git-operations
Git command patterns, branching strategy, and safety protocols. TRIGGER when: managing branches, resolving merge conflicts, or running commit/merge/push operations. SKIP: worktree lifecycle and isolation recovery (use worktree-management); CI automation (use github-actions-template).
cad-plan-checker-contract
Internal role contract, preloaded into every cad-plan-checker rung agent. Not a user command.
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.