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 agentmods add skills/tada5hi/skills/update-agent-docsnpx skills add tada5hi/skills --skill update-agent-docsgit clone --depth 1 https://github.com/tada5hi/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/tada5hi/skills/update-agent-docs)<a href="https://agentmods.dev/skills/tada5hi/skills/update-agent-docs"><img src="https://agentmods.dev/badge/skills/tada5hi/skills/update-agent-docs.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.00056 | $0.01380 |
| Opus 5 | $0.00028 | $0.00690 |
| Sonnet 5 | $0.00011 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
update-agent-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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-agent-docs
Propose improvements to the
init-agent-docsskill templates by opening a PR againsttada5hi/skills.
When to Use
- A project's agent docs have been refined and contain patterns not yet reflected in the templates
- A new section or convention was discovered during project initialization that would benefit other projects
- Template placeholders, comments, or structure need updating based on real-world usage
- The user asks to "update the skill templates", "contribute back to skills", "improve the agent docs templates", or similar
Process
1. Gather context
Read the current project's agent documentation and the current skill templates side by side:
Current project docs (in the working directory):
CLAUDE.mdAGENTS.md.agents/structure.md.agents/architecture.md.agents/testing.md.agents/conventions.md
Current skill templates (in the skills repository):
{{skills_repo_path}}/skills/init-agent-docs/templates/CLAUDE.md{{skills_repo_path}}/skills/init-agent-docs/templates/AGENTS.md{{skills_repo_path}}/skills/init-agent-docs/templates/.agents/structure.md{{skills_repo_path}}/skills/init-agent-docs/templates/.agents/architecture.md{{skills_repo_path}}/skills/init-agent-docs/templates/.agents/testing.md{{skills_repo_path}}/skills/init-agent-docs/templates/.agents/conventions.md
The skills repository is located at one of:
- Local path: ask the user, or check for a sibling
skillsdirectory (e.g.,../skillsrelative to the current project) - Remote:
https://github.com/tada5hi/skills
2. Identify improvements
Compare the project's docs against the templates and categorize findings:
| Category | Description | Example |
|---|---|---|
| New section | A section in the project docs that has no corresponding template section | A "Migration Patterns" section in architecture.md |
| Better structure | A section that exists in both but the project's version is structured more usefully | Tables instead of bullet lists, better heading hierarchy |
| New placeholder | A placeholder that would be useful but doesn't exist in the template | {{package_manager_setup}} for corepack-based projects |
| Improved guidance | Better HTML comments or instructions for agents filling in the template | More specific instructions for monorepo dependency layers |
| Stale content | Template content that no longer reflects best practices | Outdated section ordering, deprecated patterns |
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.
- 5d ago First seen · 127 lines · 56 tokens per session scan A 9eaea88442c0
update-agent-docs is a skill published in the GitHub repository tada5hi/skills (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,380 once invoked, about $0.0003 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
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…
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.
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…
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…