legacy-modernization

legacy-modernization is a skill for Claude Code from JeremyDev87/codingbuddy. It costs 34 tokens per session (1,919 once invoked), scanned A, original, MIT.

A guide for updating older software gradually while keeping it working. Legacy code is older code still used by a project, and the strangler fig pattern replaces parts of it step by step.

In plain words
What is it for?
It is for migrations such as CommonJS to ESM, framework upgrades, callback-to-async changes, JavaScript-to-TypeScript moves, deprecated API replacements, and monolith-to-module changes.
Why use it?
It helps reduce the risk of a large rewrite breaking existing behaviour.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit It is for migrations such as CommonJS to ESM, framework upgrades, callback-to-async changes, JavaScript-to-TypeScript moves, deprecated API replacements, and monolith-to-module changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeremydev87/codingbuddy/legacy-modernization
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 JeremyDev87/codingbuddy --skill legacy-modernization
Clone the repo
git clone --depth 1 https://github.com/JeremyDev87/codingbuddy

Made for: Claude Code.

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 legacy-modernization

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/legacy-modernization"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/legacy-modernization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,919 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.00034 $0.01919
Opus 5.5 $0.00014 $0.00768
Sonnet 5.5 $0.00007 $0.00384
Haiku 4.5 $0.00003 $0.00192

Measured 1mo ago against content hash a3cc9c3aa7e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

legacy-modernization 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 1mo 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.

packages/rules/.ai-rules/skills/legacy-modernization/SKILL.md · 294 lines

How it starts

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

Legacy Modernization

Overview

Legacy code isn't bad code — it's code that solved a real problem when it was written. Modernization is the process of adapting it to current requirements without breaking what works.

Core principle: Never rewrite from scratch. Strangle it incrementally. Each step must leave the system in a working state.

Iron Law:

THE SYSTEM MUST WORK AFTER EVERY CHANGE
There is no "temporarily broken while we modernize"

When to Use

  • Migrating from CommonJS to ESM
  • Upgrading major framework versions (NestJS 9 → 10)
  • Replacing callback patterns with async/await
  • Moving from JavaScript to TypeScript
  • Replacing deprecated APIs
  • Architectural migration (monolith → modules)

Assessment Phase

Inventory

Before any changes, understand what you have:

# Size and complexity
find src/ -name "*.ts" -o -name "*.js" | \
  xargs wc -l | sort -rn | head -20

# Dependency graph
npx madge --circular src/

# Test coverage (what's protected)
npx jest --coverage --coverageReporters text-summary

# Outdated packages
npm outdated

# Known patterns to modernize
grep -rn "require\(" src/ --include="*.ts" | wc -l  # CommonJS in TypeScript
grep -rn "callback\|\.then\|\.catch" src/ --include="*.ts" | wc -l  # Promises vs async
grep -rn ": any" src/ --include="*.ts" | wc -l  # Untyped code

Risk Assessment

Rate each area for modernization risk:

## Modernization Risk Register

| Module | Lines | Test Coverage | External Deps | Criticality | Risk |
|--------|-------|---------------|---------------|-------------|------|
| rules.service.ts | 120 | 85% | None | High | LOW |
| mcp.service.ts | 450 | 45% | MCP SDK | High | HIGH |
| main.ts | 60 | 0% | NestJS | Medium | MEDIUM |

Risk = (Criticality × (100 - Coverage%)) / 100

Modernization Backlog

## Modernization Items

| ID | Pattern | Count | Files | Effort |
|----|---------|-------|-------|--------|
| M-001 | `any` type → explicit types | 23 | 8 files | 2h |
| M-002 | Callbacks → async/await | 12 | 4 files | 4h |
| M-003 | CommonJS → ESM imports | 45 | 15 files | 1h |
| M-004 | NestJS 9 → NestJS 10 | 1 | package.json | 8h |

Read the full file on GitHub · 294 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. 1mo ago First seen · 294 lines · 34 tokens per session scan A a3cc9c3aa7e4

Subscribe to this mod's changes

legacy-modernization is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 1,919 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

ring:migrating-to-lib-observability

Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…

LerianStudio/ring · 104 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:instrumenting-streaming-events

Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…

LerianStudio/ring · 102 tokens

ring:planning-codebase-simplification

Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…

LerianStudio/ring · 105 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens