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 agentmods add commands/burly-mingo/modernization-kit/phase-4-modernization-plangit clone --depth 1 https://github.com/Burly-Mingo/modernization-kitWrote 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/commands/burly-mingo/modernization-kit/phase-4-modernization-plan)<a href="https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-4-modernization-plan"><img src="https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-4-modernization-plan.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00505 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
phase-4-modernization-plan 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 4: Modernization Plan
Turn the target architecture into an actionable, phased implementation plan.
Plan Components
1. Migration Phases: For each — what gets built, dependencies, data migration, deliverable (working functionality), effort estimate, risk factors, validation criteria. Order: security first → foundation → highest-pain-point modules → revenue/cost-saving → nice-to-haves. Each phase independently valuable.
2. Data Migration Strategy: Per-database/schema plan. Identity/auth migration (always hardest). Transformations. Validation. Rollback. ETL/job replacement.
3. Cutover Strategy: Build-then-cutover vs. parallel vs. strangler fig (justify). Independent cutover components. Downtime. DNS/routing. Rollback. Post-cutover monitoring.
4. Timeline Estimates:
- AI-assisted development estimates
- Traditional development estimates (comparison)
- Logistics overhead by org size:
- Small (<50): hardware procurement/setup, cloud/license setup. 1.3-1.5x multiplier.
- Mid-size (50-500): procurement, approval gates, change management, legal review. 1.5-2x.
- Large/enterprise (500+): capital budget cycles, RFP, architecture/security review boards, cross-team coordination, environment provisioning queues. 2-3x.
- Realistic calendar = development × logistics multiplier
- Long-lead-time items to start immediately
5. Cost Estimates: Development (labor). Infrastructure. Ongoing operational. Cost of doing nothing (1, 3, 5 year). Licensing eliminated.
6. Risk Assessment: Each risk: description, probability, impact, mitigation, contingency. Must include: key person dependency, scope creep, data migration errors, integration breakage, performance regression, user adoption, vendor risk, timeline/budget overrun.
7. Value-Add Features: Beyond 1:1 replacement — AI automation, analytics, customer-facing improvements, API/integration, competitive advantages. For each: what, impact, effort, phase, dependencies, ROI.
8. Open Questions: Everything unknown with assumption, why it matters, how to resolve, what changes if wrong.
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.
- 5d ago First seen · 40 lines · 0 tokens per session scan A 250c1f3bc2a8
phase-4-modernization-plan is a command published in the GitHub repository Burly-Mingo/modernization-kit (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 tokens. 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.
Other commands, from other repositories
ask
⚡ Answer technical and architectural questions.
use-mcp
Utilize tools of Model Context Protocol (MCP) servers.
cook
⚡⚡⚡ Implement a feature [step by step].
code
⚡ Start coding & testing an existing plan.
plan
⚡⚡⚡ Intelligent plan creation with prompt enhancement.
fix
⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY].