Borrowing it
Nothing to install: this file belongs to ricardoquesada/regenerator2000. 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/ricardoquesada/regenerator2000/main/.agent/skills/update-mcp-docs/SKILL.mdgit clone --depth 1 https://github.com/ricardoquesada/regenerator2000Wrote 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/ricardoquesada/regenerator2000/update-mcp-docs)<a href="https://agentmods.dev/skills/ricardoquesada/regenerator2000/update-mcp-docs"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/update-mcp-docs.svg" alt="Measured on agentmods" 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.00035 | $0.00184 |
| Opus 5 | $0.00017 | $0.00092 |
| Sonnet 5 | $0.00007 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
update-mcp-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 8d 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.
What it actually says
Update MCP Docs Skill
This skill introspects the running MCP server and automatically updates the "Available Tools" section in docs/mcp.md.
Usage
Simply run:
.agent/skills/update-mcp-docs/scripts/run_update.sh
This will:
- Build and start the MCP server (if not already running).
- Query the
tools/listendpoint. - specific table of tools, arguments, and descriptions.
- Update
docs/mcp.md.
When to Use
Run this skill whenever you add, modify, or remove a tool in crates/regenerator2000-core/src/mcp/handler.rs to ensure documentation stays in sync.
What ships with it
3 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.
- 8d ago First seen · 28 lines · 35 tokens per session scan A 1614e01d3f98
update-mcp-docs is a skill published in the GitHub repository ricardoquesada/regenerator2000 (164 stars, last pushed 13d ago), licensed Apache-2.0. It adds 35 tokens to every session and 184 once invoked, about $0.0002 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
c64-development
Use when developing, running, or debugging Commodore 64 software (Commodore BASIC or 6510/6502 assembly) on the VICE emulator with the c64 CLI or the c64-tools MCP server. Covers the build/run/observe/debug loop, the stopped-state discipline, C64 text encodings, graphics and sprites, and the memory map.
6502-assembly
Use when writing or debugging 6502 assembly for the Commodore 64 with ca65/ld65 via c64 build or c64 run. Covers the C64 program skeleton, the BASIC SYS stub, calling ROM routines, and 6502 gotchas.
cartridge-programming
Use when writing, building, or debugging a Commodore 64 cartridge — plain 8K/16K/Ultimax or bank-switched EasyFlash — with the c64 CLI or the c64-tools MCP server. Covers the two boot mechanisms (CBM80 vs the $FFFC reset vector), the memory modes, cart-native code in ROM, the EasyFlash banking discipline from…
6502-debugging
Use when a C64 program misbehaves at runtime — crashes, corruption, wrong values, dead input, visual glitches — and you need a procedure, not a guess. Symptom-indexed playbook of runtime debugging procedures using c64-tools.
disk-io-programming
Use when a Commodore 64 program has to touch a disk while it runs — loading levels, music or graphics on demand, saving a high-score file, or streaming a data file byte by byte. Covers the KERNAL LOAD/SAVE and channel calls, device and secondary-address conventions, reading the DOS error channel, and the…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…