Borrowing it
Nothing to install: this file belongs to testdino-hq/testdino-mcp. 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/testdino-hq/testdino-mcp/main/.claude/skills/update-docs/SKILL.mdgit clone --depth 1 https://github.com/testdino-hq/testdino-mcpWrote 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/testdino-hq/testdino-mcp/update-docs)<a href="https://agentmods.dev/skills/testdino-hq/testdino-mcp/update-docs"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/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/testdino-hq/testdino-mcp/update-docs"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/update-docs.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.00022 | $0.00508 |
| Opus 5 | $0.00011 | $0.00254 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update documentation: $ARGUMENTS
Workflow
Step 1 — Determine Scope
If a specific tool is named:
- Read the tool's source file to understand current behavior
- Check
docs/TOOLS.mdfor the tool's existing documentation - Check
docs/skill.mdfor any references
If "all" is specified:
- Read all tool source files
- Compare against
docs/TOOLS.mdfor drift - Check tool count in
README.md
Step 2 — Check for Drift
For each tool in scope, verify:
-
TOOLS.md
- Does the documented tool name match
toolDefinition.name? - Does the parameter list match
inputSchema.properties? - Are required/optional fields correctly documented?
- Do example requests match the actual schema?
- Are enum values listed and up to date?
- Does the documented tool name match
-
skill.md
- Are workflow references to tools still accurate?
- Do decision trees point to the right tools?
- Are parameter quick-reference tables current?
-
README.md
- Is the tool count correct?
- Are all tool names listed?
- Do feature descriptions match reality?
-
INSTALLATION.md
- Are setup instructions still valid?
- Is the package name and version reference correct?
Step 3 — Update
Fix any drift found. Follow the existing documentation style — don't reinvent the format.
For TOOLS.md, each tool section should include:
- Tool name and description
- Parameters table (name, type, required/optional, description)
- Example usage (request + response)
- Notes on when to use vs similar tools
Step 4 — Verify
- Read the updated docs to confirm they're accurate
- Check for broken markdown formatting
- Run
npm run formatto ensure consistent formatting
Rules
- Don't rewrite documentation that's already correct — only fix drift
- Match existing documentation style and structure
- Tool descriptions in docs should be more detailed than the inputSchema description (docs are for humans, schema is for AI agents)
- If a tool was removed, remove its documentation section entirely — don't leave stubs
- Keep skill.md focused on AI agent patterns, not human-readable reference
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.
- 9d ago First seen · 74 lines · 22 tokens per session scan A 1546eeea7c32
update-docs is a skill published in the GitHub repository testdino-hq/testdino-mcp (9 stars, last pushed 29d ago), licensed MIT. It adds 22 tokens to every session and 508 once invoked, about $0.0001 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…