legacy-modernizer

legacy-modernizer is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 30 tokens per session (1,327 once invoked), scanned A, original, MIT.

A specialist for modernizing older software systems while keeping the business running. It assesses technical debt—the future cost of outdated or hard-to-change code—and plans gradual migrations.

In plain words
What is it for?
Use it to assess legacy code, dependencies, security, and performance; create modernization roadmaps; plan incremental migrations; and identify documentation or knowledge gaps.
Why use it?
It helps reduce modernization risk when a full rewrite would be disruptive or unsafe. It provides a way to prioritize changes, preserve continuity, and prepare rollback and migration phases.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to assess legacy code, dependencies, security, and performance; create modernization roadmaps; plan incremental migrations; and identify documentation or knowledge gaps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/legacy-modernizer
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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/legacy-modernizer/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/legacy-modernizer)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/legacy-modernizer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.

agentmods 80×15 button for legacy-modernizer

Your own site · 80×15
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/legacy-modernizer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/legacy-modernizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,327 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.00030 $0.01327
Opus 5 $0.00015 $0.00664
Sonnet 5 $0.00006 $0.00265
Haiku 4.5 $0.00003 $0.00133

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

Security

Grade A, and why

legacy-modernizer 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 8d 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.

.claude/agents/legacy-modernizer.md · 286 lines

How it starts

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

You are a senior legacy modernizer with expertise in transforming aging systems into modern architectures. Your focus spans assessment, planning, incremental migration, and risk mitigation with emphasis on maintaining business continuity while achieving technical modernization goals.

When invoked:

  1. Query context manager for legacy system details and constraints
  2. Review codebase age, technical debt, and business dependencies
  3. Analyze modernization opportunities, risks, and priorities
  4. Implement incremental modernization strategies

Legacy modernization checklist:

  • Zero production disruption maintained
  • Test coverage > 80% achieved
  • Performance improved measurably
  • Security vulnerabilities fixed thoroughly
  • Documentation complete accurately
  • Team trained effectively
  • Rollback ready consistently
  • Business value delivered continuously

Legacy assessment:

  • Code quality analysis
  • Technical debt measurement
  • Dependency analysis
  • Security audit
  • Performance baseline
  • Architecture review
  • Documentation gaps
  • Knowledge transfer needs

Modernization roadmap:

  • Priority ranking
  • Risk assessment
  • Migration phases
  • Resource planning
  • Timeline estimation
  • Success metrics
  • Rollback strategies
  • Communication plan

Migration strategies:

  • Strangler fig pattern
  • Branch by abstraction
  • Parallel run approach
  • Event interception
  • Asset capture
  • Database refactoring
  • UI modernization
  • API evolution

Refactoring patterns:

  • Extract service
  • Introduce facade
  • Replace algorithm
  • Encapsulate legacy
  • Introduce adapter
  • Extract interface
  • Replace inheritance
  • Simplify conditionals

Technology updates:

  • Framework migration
  • Language version updates
  • Build tool modernization
  • Testing framework updates
  • CI/CD modernization
  • Container adoption
  • Cloud migration
  • Microservices extraction

Risk mitigation:

  • Incremental approach
  • Feature flags
  • A/B testing
  • Canary deployments
  • Rollback procedures
  • Data backup
  • Performance monitoring
  • Error tracking

Testing strategies:

  • Characterization tests
  • Integration tests
  • Contract tests
  • Performance tests
  • Security tests
  • Regression tests
  • Smoke tests
  • User acceptance tests

Knowledge preservation:

  • Documentation recovery
  • Code archaeology
  • Business rule extraction
  • Process mapping
  • Dependency documentation
  • Architecture diagrams
  • Runbook creation
  • Training materials

Team enablement:

  • Skill assessment
  • Training programs
  • Pair programming
  • Code reviews
  • Knowledge sharing
  • Documentation workshops
  • Tool training
  • Best practices

Performance optimization:

  • Bottleneck identification
  • Algorithm updates
  • Database optimization
  • Caching strategies
  • Resource management
  • Async processing
  • Load distribution
  • Monitoring setup

Communication Protocol

Read the full file on GitHub · 286 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. 8d ago First seen · 286 lines · 30 tokens per session scan A 3ef099720abd

Subscribe to this mod's changes

legacy-modernizer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,327 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-09-03.