deprecation-and-migration

deprecation-and-migration is a skill for Claude Code from GuillemRoca/agent-skills-android. It costs 48 tokens per session (1,812 once invoked), scanned A, original, MIT.

A guide for safely retiring old APIs, libraries, Android versions, feature flags, or other legacy code while moving users and code to replacements.

In plain words
What is it for?
Use it when adding deprecation notices, raising Android minimum versions, upgrading Kotlin or Compose, replacing Android APIs, or moving from XML layouts to Compose.
Why use it?
It helps prevent broken callers and unmanaged migration risk by checking usage, alternatives, maintenance cost, and rollback concerns first.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agent-skills-android plugin — 29 skills, 7 commands, 3 agents, 1 hook shipped together

Good fit Use it when adding deprecation notices, raising Android minimum versions, upgrading Kotlin or Compose, replacing Android APIs, or moving from XML layouts to Compose.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/guillemroca/agent-skills-android/deprecation-and-migration
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 GuillemRoca/agent-skills-android --skill deprecation-and-migration
Clone the repo
git clone --depth 1 https://github.com/GuillemRoca/agent-skills-android

Made for: Claude Code.

Or install agent-skills-android, the plugin that ships this one along with the rest of its 29 skills, 7 commands, 3 agents, 1 hook.

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-and-migration

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/guillemroca/agent-skills-android/deprecation-and-migration"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/deprecation-and-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,812 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.
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.00048 $0.01812
Opus 5 $0.00024 $0.00906
Sonnet 5 $0.00010 $0.00362
Haiku 4.5 $0.00005 $0.00181

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

Security

Grade A, and why

deprecation-and-migration 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.

skills/deprecation-and-migration/SKILL.md · 218 lines

How it starts

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

Deprecation and Migration

Overview

"Code is a liability, not an asset." Every line of code carries ongoing maintenance cost. Deprecation and migration are how you manage that liability — removing what's no longer needed and upgrading what must evolve. Hyrum's Law applies: once systems have users, simple announcements aren't enough.

When to Use

  • Bumping minSdk or targetSdk
  • Migrating to a new library version (Room, Compose, Kotlin)
  • Replacing deprecated Android APIs
  • Removing legacy feature flags or dead code
  • Migrating from XML to Compose
  • Upgrading from Java to Kotlin in existing modules

Skip when: The code has no callers and can be deleted outright.

Core Process

Step 1: Decision Framework

  1. Assess before deprecating:
Question Impact
How many callers exist? grep/find usages to count
Is there a replacement ready? Never deprecate without an alternative
What's the maintenance cost of keeping it? Security risk? Build complexity?
What's the migration cost? Test effort, rollback risk
Is there a deadline? (security, API level) Compulsory vs advisory
  1. Deprecation types:
    • Advisory: Migration recommended but not required on a timeline
    • Compulsory: Hard deadline (security fix, API level requirement, Play Store policy)

Step 2: Deprecate with Guidance

  1. Use Kotlin's @Deprecated with replacement:
@Deprecated(
    message = "Use TaskRepository.getTasks() with Flow instead",
    replaceWith = ReplaceWith(
        expression = "getTasks()",
        imports = ["com.example.data.TaskRepository"]
    ),
    level = DeprecationLevel.WARNING  // WARNING → ERROR → HIDDEN
)
suspend fun getTaskList(): List<Task> = getTasks().first()
  1. Deprecation levels:

    • WARNING — compile-time warning, still usable
    • ERROR — compile-time error, forces migration
    • HIDDEN — invisible in IDE, only for binary compatibility
  2. Progression:

    Phase 1: Add @Deprecated(WARNING) + replacement guidance
    Phase 2: Migrate all internal callers
    Phase 3: Escalate to @Deprecated(ERROR)
    Phase 4: Remove (or HIDDEN for library backward compatibility)
    

Read the full file on GitHub · 218 lines

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. 12d ago First seen · 218 lines · 48 tokens per session scan A fc2805e8fce2

Subscribe to this mod's changes

deprecation-and-migration is a skill published in the GitHub repository GuillemRoca/agent-skills-android (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,812 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-31.

Related

Other skills, from other repositories

spec-kitty-mission-system

Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…

Priivacy-ai/spec-kitty · 160 tokens

spec-kitty-git-workflow

Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…

Priivacy-ai/spec-kitty · 125 tokens

spec-kitty-spdd-reasons

Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…

Priivacy-ai/spec-kitty · 118 tokens

spec-kitty-runtime-review

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…

Priivacy-ai/spec-kitty · 85 tokens

spk-doctrine-show-me

Explain Spec Kitty work with compact, checkable visuals. Use for specs, plans, architecture, control flow, diffs, status boards, or whenever prose obscures structure.

Priivacy-ai/spec-kitty · 42 tokens

spk-admin-dashboard

Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.

Priivacy-ai/spec-kitty · 39 tokens