Borrowing it
Nothing to install: this file belongs to WolframResearch/AgentTools. 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/WolframResearch/AgentTools/main/.claude/skills/update-docs/SKILL.mdgit clone --depth 1 https://github.com/WolframResearch/AgentToolsWrote 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/wolframresearch/agenttools/update-docs)<a href="https://agentmods.dev/skills/wolframresearch/agenttools/update-docs"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/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/wolframresearch/agenttools/update-docs"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/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.00015 | $0.00779 |
| Opus 5.5 | $0.00006 | $0.00312 |
| Sonnet 5.5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation for Branch Changes
Review all changes on the current branch compared to a base branch and update markdown documentation files to reflect those changes.
Base branch: Use $ARGUMENTS if provided, otherwise default to main.
Process
1. Understand the Changes
Start by identifying what changed on the current branch:
- Run
git diff <base>...HEAD --statto see which files changed - Run
git log <base>..HEAD --onelineto understand the commit history
Then fully read and explore every changed source file (not just tests or assets) until you completely understand the changes. The diff alone does not provide enough context — you must read the full files to understand how the changes fit into the surrounding code, what patterns are used, and what the code actually does.
For each changed source file:
- Read the entire file (or at minimum the complete functions/sections that were modified)
- Understand the purpose of the file and how the changes relate to its overall role
- Follow references to other files if needed to understand dependencies or shared symbols
- If a new file was added, read it completely
Build a thorough mental model of:
- What new features, modules, or capabilities were added
- What existing behavior changed
- What new files, symbols, options, or configuration were introduced
- What was removed or renamed
- How the changes interact with the rest of the codebase
2. Inventory Documentation Files
Read ALL markdown documentation files that could be affected:
AGENTS.md(project structure, development patterns, file listings)README.md(features, tools, options, API reference)- Every file in
docs/(tools, servers, clients, prompts, apps, testing, building, getting-started, etc.)
3. Identify What Needs Updating
For each documentation file, check whether the changes on the branch affect any of its content:
- Project structure listings - Do they include new files/directories?
- Feature lists - Do they mention new capabilities?
- Tool tables - Do they list new tools or note changed tool behavior?
- Option/config tables - Do they document new options or environment variables?
- Server descriptions - Do they reflect changes to server configurations?
- Related files sections - Do they reference new source files?
- Cross-references/links - Are there broken links to renamed/removed sections?
- Code examples - Are they still accurate?
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 · 82 lines · 15 tokens per session scan A 90e1330d6c8d
update-docs is a skill published in the GitHub repository WolframResearch/AgentTools (96 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 779 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 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.