Borrowing it
Nothing to install: this file belongs to malwarebo/nyrve. 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/malwarebo/nyrve/main/.github/skills/tool-rename-deprecation/SKILL.mdgit clone --depth 1 https://github.com/malwarebo/nyrveWrote 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/malwarebo/nyrve/tool-rename-deprecation)<a href="https://agentmods.dev/skills/malwarebo/nyrve/tool-rename-deprecation"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/tool-rename-deprecation/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/malwarebo/nyrve/tool-rename-deprecation"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/tool-rename-deprecation.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.00060 | $0.02404 |
| Opus 5 | $0.00030 | $0.01202 |
| Sonnet 5 | $0.00012 | $0.00481 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
tool-rename-deprecation 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 12d 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.
This is a copy
100% identical to tool-rename-deprecation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Rename Deprecation
When a tool or tool set reference name is changed, the old name must always be added to the deprecated/legacy array so that existing prompt files, tool configurations, and saved references continue to resolve correctly.
When to Use
Run this skill on any change to built-in tool or tool set registration code to catch regressions:
- Renaming a tool's
toolReferenceName - Renaming a tool set's
referenceName - Moving a tool from one tool set to another (the old
toolSet/toolNamepath becomes a legacy name) - Reviewing a PR that modifies tool registration — verify no legacy names were dropped
Procedure
Step 1 — Identify What Changed
Determine whether you are renaming a tool or a tool set, and where it is registered:
| Entity | Registration | Name field to rename | Legacy array | Stable ID (NEVER change) |
|---|---|---|---|---|
Tool (IToolData) |
TypeScript | toolReferenceName |
legacyToolReferenceFullNames |
id |
| Tool (extension) | package.json languageModelTools |
toolReferenceName |
legacyToolReferenceFullNames |
name (becomes id) |
Tool set (IToolSet) |
TypeScript | referenceName |
legacyFullNames |
id |
| Tool set (extension) | package.json languageModelToolSets |
name or referenceName |
legacyFullNames |
— |
Critical: For extension-contributed tools, the name field in package.json is mapped to id on IToolData (see languageModelToolsContribution.ts line id: rawTool.name). It is also used for activation events (onLanguageModelTool:<name>). Never rename the name field — only rename toolReferenceName.
Step 2 — Add the Old Name to the Legacy Array
Verify the old toolReferenceName value appears in legacyToolReferenceFullNames. Don't assume it's already there — check the actual array contents. If the old name is already listed (e.g., from a previous rename), confirm it wasn't removed. If it's not there, add it.
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.
- 12d ago First seen · 150 lines · 60 tokens per session scan A e8f9a414e748
tool-rename-deprecation is a skill published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 2,404 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tool-rename-deprecation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github-issue-manager
Classifies a user request as Bug, Compatibility, Feature, Question, or Task for the explyt/spring-plugin GitHub repo, lightly researches the relevant codebase, searches similar existing issues, and either reports an existing issue or creates a correctly titled and labeled one following the repository issue forms. Use…
github-bugs-triage
Triages the open bug queue of the explyt/spring-plugin GitHub repository: fetches the oldest open plugin-bug and compatibility issues, refines titles, suggests labels and priorities with evidence, detects duplicates, and writes a structured triage table. Use when asked to triage spring-plugin bugs, review the bug…
org2-performance-guard
Prevent CPU, RAM, I/O, background-work, and false-green lifecycle regressions in ORG2. Use when adding or reviewing polling, timers, Realtime subscriptions, event listeners, workers, streaming paths, caches, pagination, provider-owned transcript ingestion or identity/dedupe, external-history scans, cloud sync…
Debug
Use logging calls for in-depth debugging via local log files.
playwriter
A command-line tool for controlling the user's currently open Chrome tab through Playwriter. It can inspect the page, perform browser actions, and collect console output.
fix-sentry-issues
A workflow for investigating Sentry, a service that collects errors from live software, and fixing their underlying causes. It requires a Sentry MCP service.