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 tldrgit 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)<a href="https://agentmods.dev/skills/qurore/speckit-tldr/tldr"><img src="https://agentmods.dev/badge/skills/qurore/speckit-tldr/tldr/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"><img src="https://agentmods.dev/badge/skills/qurore/speckit-tldr/tldr.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.00141 | $0.01742 |
| Opus 5 | $0.00071 | $0.00871 |
| Sonnet 5 | $0.00028 | $0.00348 |
| Haiku 4.5 | $0.00014 | $0.00174 |
Grade A, and why
tldr 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit TLDR
Produce a fast, review-oriented overview of Spec Kit spec.md / plan.md files.
The goal is to cut the time a PR reviewer spends getting oriented, while
deliberately surfacing the spots that deserve close reading rather than hiding
them. A TLDR here is an entry point into the document, not a substitute for it.
Core principles (read first)
- Regenerate from the canonical source. Always extract from the actual files in the repo / PR. Never trust a pre-existing summary an author may have written; a summary's omissions become the reviewer's blind spots.
- Surface risk, don't smooth it over. Ambiguities, missing acceptance criteria, and unanswered questions go to the top, not buried. The summary's job is to point at what to scrutinize.
- Point back into the document. Every extracted item records its source file and (when available) heading/line, so the reviewer can jump to the full text.
- Be diff-aware. Reviewers review the change, not the whole document. Mark what this PR added/changed and let the reviewer filter to just that.
Step 1 — Resolve scope and target files
Parse the invocation argument ($ARGUMENTS), and also honor natural language in
the user's message. Resolution order:
- A path argument (e.g.
specs/042-foo/plan.md) → operate on exactly that file; detect spec vs plan from the filename. spec/plan→ restrict to that artifact type.both(or no argument) → process bothspec.mdandplan.mdfor the target feature.- Natural language overrides/refines the argument: "just the plan", "spec only", "tldr the auth feature spec" → scope accordingly.
To find the feature directory when no path is given:
- If the user names a feature, glob
specs/*<feature>*/. - Otherwise infer from the current PR/branch: the changed
specs/<feature>/*.mdfiles (see Step 2). If still ambiguous, list the candidates underspecs/and ask which feature.
Spec Kit convention: each feature lives in specs/<NNN-feature-name>/ with
spec.md, plan.md, and often research.md, data-model.md, contracts/,
tasks.md. Only spec.md and plan.md are in scope for this skill.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 148 lines · 141 tokens per session scan A 5f12bf9dd697
tldr is a skill published in the GitHub repository qurore/speckit-tldr (3 stars, last pushed 2mo ago), licensed MIT. It adds 141 tokens to every session and 1,742 once invoked, about $0.0007 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-31.
Other skills, from other repositories
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…