Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. 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/matteocervelli/llms/main/.claude/skills/registry/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/registry)<a href="https://agentmods.dev/skills/matteocervelli/llms/registry"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/registry.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.00072 | $0.02867 |
| Opus 5 | $0.00036 | $0.01434 |
| Sonnet 5 | $0.00014 | $0.00573 |
| Haiku 4.5 | $0.00007 | $0.00287 |
Grade A, and why
registry 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 3d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Registry
PDCA lifecycle management for all Claude Code system components.
Usage
/registry # Dashboard — counts + stale warnings
/registry list [type] # List components (skills, agents, rules, hooks, plugins)
/registry check <name> # Full detail for one component
/registry update # Scan filesystem, add new components, preserve manual fields
/registry scan # Integrity check (broken refs, orphans, missing frontmatter)
/registry stale [days] # Components not tested in N days (default: 30)
/registry deprecate <name> # Deprecate a skill: move to _archived/, update registry.yaml
Data Store
~/.claude/docs/development/registry.yaml — single YAML file, version-controlled.
Subcommand Details
/registry (default) — Dashboard
Read registry.yaml and produce a summary:
## Component Registry Dashboard
| Type | Count | Act | Check | Do | Plan | Stale (>30d) |
| ------- | ----- | --- | ----- | --- | ---- | ------------ |
| Skills | 38 | 12 | 5 | 8 | 13 | 20 |
| Agents | 2 | 0 | 1 | 1 | 0 | 2 |
| Rules | 12 | 8 | 2 | 1 | 1 | 5 |
| Hooks | 7 | 5 | 1 | 1 | 0 | 3 |
| Plugins | 7 | 4 | 2 | 1 | 0 | 2 |
**Warnings**: 32 components not tested in >30 days.
/registry list [type] — List Components
List all components, optionally filtered by type.
Output format per component:
[pdca_status] name — why (last_manual_test)
Example:
Skills (38):
[act] security — Single entry point for security guidance (2026-02-14)
[act] review — Unified review dispatcher (2026-02-14)
[plan] analytics — DB query helper (never tested)
...
Deprecated (2):
[deprecated] example-skill — Replaced by /unified (deprecated 2026-03-09, remove by 2026-06-07)
[deprecated] old-helper — No longer needed (deprecated 2026-02-01, OVERDUE: was due 2026-05-02)
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.
- 3d ago First seen · 291 lines · 72 tokens per session scan A 738325cc0223
registry is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 2,867 once invoked, about $0.0004 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-09-03.
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…
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…