Borrowing it
Nothing to install: this file belongs to warpdotdev/common-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/warpdotdev/common-skills/main/.agents/skills/scan-new-specs/SKILL.mdgit clone --depth 1 https://github.com/warpdotdev/common-skillsWrote 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/warpdotdev/common-skills/scan-new-specs)<a href="https://agentmods.dev/skills/warpdotdev/common-skills/scan-new-specs"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/scan-new-specs.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.1 | $0.00106 | $0.00640 |
| Opus 5 | $0.00053 | $0.00320 |
| Sonnet 5 | $0.00021 | $0.00128 |
| Haiku 4.5 | $0.00011 | $0.00064 |
Grade A, and why
scan-new-specs 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 7d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scan-new-specs (deprecated)
Retired 2026-08-20. Do not invoke this skill and do not schedule it.
Its scheduled agent (0ITuF9vNJ1RiO00Szlm1fW) is paused and stays paused.
Why it was retired
The skill fired on spec merge, which happens before a feature ships. Two failures followed from that single design choice:
- It drafted docs for unreleased and sometimes abandoned work. A merged spec is not a shipped feature. The agent had no evidence of what users had actually received, so pages were written for behavior that had not landed, or had landed differently, or never landed at all.
- It treated every spec as a docs task. Nothing asked whether a change warranted documentation. Pure UI changes, small intuitive additions, and behind-the-scenes work all became draft PRs, and the docs repo accumulated unvetted content debt faster than anyone could review it.
What replaces it
The missing_docs skill in warpdotdev/docs, running in drift-watch mode. It differs in the two ways that matter:
- Release-triggered.
scripts/check_new_release.pygates each run on a new stable release, so the pipeline sees what actually shipped rather than what was planned. A daily schedule does per-release work. - Gated on worthiness. Every candidate is evaluated against
.agents/references/docs-worthiness-criteria.mdbefore anything is drafted, with a default of no docs and a requirement to name concrete evidence. Verdicts, including rejections, are recorded inreferences/changelog_decisions.mdso nothing is re-litigated.
Anything genuinely worth documenting re-surfaces there once it ships.
If you were about to run this
- Looking for docs gaps? Run
missing_docsin drift-watch mode from thewarpdotdev/docsrepo. - You are an engineer who wants docs for your feature? Invoke
write-feature-docsdirectly and interactively. It still works, and it still walks you through spec research and outline confirmation. It no longer runs headlessly. - Setting up a scheduled docs agent? Use
missing_docs, not this. Scheduling this skill reintroduces exactly the flooding it was retired for.
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.
- 7d ago First seen · 38 lines · 106 tokens per session scan A ad988432e8a7
scan-new-specs is a skill published in the GitHub repository warpdotdev/common-skills (537 stars, last pushed 4d ago), licensed MIT. It adds 106 tokens to every session and 640 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…