deprecation

deprecation is a skill for Claude Code, Codex from ericrisco/rsc-harness. It costs 65 tokens per session (1,408 once invoked), scanned A, original, MIT.

A controlled process for retiring a public API, feature, integration, service, or legacy path while moving its users to a supported replacement.

In plain words
What is it for?
It helps inventory users, classify migration requirements, provide compatibility and migration tools, notify consumers, monitor usage, and remove the old interface when evidence supports it.
Why use it?
It reduces the chance of breaking consumers who may be hidden in external systems, old versions, or offline processes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps inventory users, classify migration requirements, provide compatibility and migration tools, notify consumers, monitor usage, and remove the old interface when evidence supports it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ericrisco/rsc-harness/deprecation
Install

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.

Any agent
npx skills add ericrisco/rsc-harness --skill deprecation
Clone the repo
git clone --depth 1 https://github.com/ericrisco/rsc-harness

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for deprecation

README.md
[![agentmods](https://agentmods.dev/badge/skills/ericrisco/rsc-harness/deprecation/github.svg)](https://agentmods.dev/skills/ericrisco/rsc-harness/deprecation)
Your own site
<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/deprecation"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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.

agentmods 80×15 button for deprecation

Your own site · 80×15
<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/deprecation"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/deprecation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.01408
Opus 5 $0.00032 $0.00704
Sonnet 5 $0.00013 $0.00282
Haiku 4.5 $0.00006 $0.00141

Measured 5d ago against content hash b9015fdea4a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 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.

skills/deprecation/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

deprecation — removal is a consumer migration

Deprecation is not a date in a changelog. It is the controlled transfer of real consumers from an old contract to a supported replacement, followed by evidence that removal no longer breaks anyone important.

This skill owns the cross-consumer program. It delegates the replacement interface to ../api-design/SKILL.md, live schema mechanics to ../db-migrations/SKILL.md, release/version mechanics to ../git-workflow/SKILL.md, and rollout/rollback execution to ../deployment/SKILL.md.

The retirement sequence

INVENTORY → CLASSIFY → ENABLE → NOTIFY → MIGRATE → OBSERVE → REMOVE

1. INVENTORY the contract and consumers

Identify:

  • exact endpoints, events, schemas, flags, SDK methods, jobs, services and docs being retired;
  • internal and external consumers, owners and contractual notice periods;
  • traffic/usage by consumer, version and operation;
  • data written only by the old path and compatibility obligations;
  • support, reseller or offline consumers invisible to runtime telemetry;
  • current fallback and restoration options.

“No known users” is not an inventory. Query telemetry, code search, dependency graphs, access keys, support records and account owners. Record where visibility is incomplete.

2. CLASSIFY the migration

  • Advisory: the old path remains supported; migration is encouraged for benefit or future-proofing.
  • Compulsory: support will end or continued use creates unacceptable security, reliability, legal or operating risk.

Only compulsory migrations justify a removal deadline. State the forcing reason and who has authority to accept exceptions. A deadline should respect contracts, effort and evidence; do not import a universal 30/60/90-day calendar.

3. ENABLE migration before announcing removal

The replacement must be usable first:

  • compatible contract or adapter where feasible;
  • migration guide with old → new mappings and changed semantics;
  • tooling, codemod, SDK or dual-write/read path for repetitive work;
  • test/sandbox path and representative examples;
  • rollback or temporary compatibility mode;
  • ownership for data backfill and reconciliation.

Read the full file on GitHub · 124 lines

Files

What ships with it

2 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.

Changes

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.

  1. 5d ago First seen · 124 lines · 65 tokens per session scan A b9015fdea4a3

Subscribe to this mod's changes

deprecation is a skill published in the GitHub repository ericrisco/rsc-harness (70 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,408 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-09-03.