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.
npx skills add eric861129/SKILLS_All-in-one --skill legacy-modernizergit clone --depth 1 https://github.com/eric861129/SKILLS_All-in-oneWrote 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/eric861129/skills_all-in-one/legacy-modernizer)<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/legacy-modernizer"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/legacy-modernizer/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/eric861129/skills_all-in-one/legacy-modernizer"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/legacy-modernizer.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.00069 | $0.01244 |
| Opus 5 | $0.00034 | $0.00622 |
| Sonnet 5 | $0.00014 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
legacy-modernizer scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
return self._new.fetch(order_id) This is a copy
94% identical to legacy-modernizer — 2 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Modernizer
Core Workflow
-
Assess system — Analyze codebase, dependencies, risks, and business constraints. Produce a dependency map and risk register before proceeding.
- Validation checkpoint: Confirm all external integrations and data contracts are documented before moving to step 2.
-
Plan migration — Design an incremental roadmap with explicit rollback strategies per phase. Reference
references/system-assessment.mdfor code analysis templates.- Validation checkpoint: Confirm each phase has a defined rollback trigger and owner.
-
Build safety net — Create characterization tests and monitoring before touching production code. Target 80%+ coverage of existing behavior.
- Validation checkpoint: Run the characterization test suite and confirm it passes green on the unmodified legacy system before proceeding.
-
Migrate incrementally — Apply strangler fig pattern with feature flags. Route traffic via a facade; shift load gradually.
- Validation checkpoint: Verify error rates and latency metrics remain within baseline thresholds after each traffic increment (e.g., 5% → 25% → 50% → 100%).
-
Validate & iterate — Run full test suite, review monitoring dashboards, and confirm business behavior is preserved before retiring legacy code.
- Validation checkpoint: New code must be proven stable at 100% traffic for at least one release cycle before legacy path is removed.
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Strangler Fig | references/strangler-fig-pattern.md |
Incremental replacement, facade layer, routing |
| Refactoring | references/refactoring-patterns.md |
Extract service, branch by abstraction, adapters |
| Migration | references/migration-strategies.md |
Database, UI, API, framework migrations |
| Testing | references/legacy-testing.md |
Characterization tests, golden master, approval |
| Assessment | references/system-assessment.md |
Code analysis, dependency mapping, risk evaluation |
What ships with it
5 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.
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.
- 9d ago First seen · 138 lines · 69 tokens per session scan A cdef74f9bcfe
legacy-modernizer is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,244 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 94% identical to legacy-modernizer, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".
backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".
apache-kafka-knowledge-patch
Use this skill when upgrading, configuring, extending, or operating Apache Kafka and its clients, Kafka Streams, Kafka Connect, MirrorMaker, KRaft, share groups, or tiered storage. Inspect the project's actual broker, client, metadata, and Java versions before applying version-dependent advice.
authjs-knowledge-patch
Use this patch to choose the maintained authentication path, avoid security-sensitive provider mistakes, and apply current Auth.js integration patterns. Read the topic reference before changing an affected flow; the quick reference prioritizes breaking behavior, security updates, and common implementation work.
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
clerk-knowledge-patch
Use this guide when implementing, upgrading, or debugging Clerk authentication, authorization, Organizations, Billing, SDKs, components, or deployment architecture. Start with the migration notes, then open the matching reference.