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 escapeboy/ai-prompts --skill update-docsgit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/escapeboy/ai-prompts/update-docs)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/update-docs"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/update-docs/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/escapeboy/ai-prompts/update-docs"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01441 |
| Opus 5.5 | $0.00021 | $0.00576 |
| Sonnet 5.5 | $0.00011 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
update-docs 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 27d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-docs — Documentation Updater
Keeps your Claude Code configuration documentation current with the latest Claude API changes, best practices, and framework updates. Searches the web, compares findings to existing docs, and applies targeted updates.
Especially useful for keeping ~/.claude/ system prompts, skill files, and project memories accurate after Claude API updates.
Scope:
/update-docshandles external freshness — API / model / pricing / beta-header drift sourced from the web. For internal consistency (dead links, README↔CHANGELOG version parity, terminology, stray Cyrillic, privacy leaks) use/content-reviewinstead. The two are complementary, not overlapping — don't duplicate content-review's checks here.
When to Use This Skill (and When NOT to)
| Use this skill for | Use a simpler approach for |
|---|---|
| Refreshing docs after a Claude API / model / pricing / beta-header change | Fixing a single known-stale value you already have the correct source for — just edit it |
A periodic sweep for staleness across ~/.claude/, skills, or memories |
Internal-consistency issues (dead links, version parity, terminology) → /content-review |
| Comparing live web/authoritative facts against what the docs currently claim | A fact you can confirm from the bundled claude-api skill in one read — read it and edit |
| A multi-file update that must stay in sync (frontmatter + config + compat lines + pricing tables) | A one-line typo or wording tweak with no external source to verify |
Start simple. Reach for this skill only when the update depends on external freshness you have to research, or spans enough files that a systematic research → analyze → update pass beats hand-editing.
Usage
/update-docs [action] [target]
What ships with it
2 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.
- 27d ago Changed 8c3a8a94f545
- 1mo ago First seen · 95 lines · 53 tokens per session scan A 3732ea3fa10a
update-docs is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 15d ago), licensed MIT. It adds 53 tokens to every session and 1,441 once invoked, about $0.0002 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 skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…