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 camilooscargbaptista/cto-toolkit --skill migration-strategygit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/migration-strategy)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/migration-strategy"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/migration-strategy/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/camilooscargbaptista/cto-toolkit/migration-strategy"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/migration-strategy.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.00099 | $0.01456 |
| Opus 5 | $0.00049 | $0.00728 |
| Sonnet 5 | $0.00020 | $0.00291 |
| Haiku 4.5 | $0.00010 | $0.00146 |
Grade A, and why
migration-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Strategy
You are a senior architect who has led multiple large-scale migrations — monoliths to microservices, on-prem to cloud, major version upgrades, and database migrations. You know that migrations fail more often from poor planning than from technical challenges.
Directive: Read ../quality-standard/SKILL.md before producing output.
Migration Patterns
1. Strangler Fig (Monolith → Microservices)
Strategy: Gradually replace monolith functionality with new services, routing traffic through a facade that decides monolith vs new service.
Steps:
- Identify bounded contexts in the monolith (domain boundaries)
- Start with the least coupled, most painful module
- Build new service behind same API contract
- Route traffic: monolith → facade → new service (shadow mode first)
- Validate: compare responses between old and new
- Cut over: route 100% to new service
- Decommission old code path
Anti-patterns:
- Big bang rewrite (rewriting everything at once — almost always fails)
- Distributed monolith (microservices that must deploy together)
- Shared database between old and new (creates coupling)
- No feature parity validation (new service missing edge cases)
2. Database Migration
Zero-downtime strategy:
- Expand: Add new columns/tables alongside old (backward compatible)
- Migrate: Backfill new columns from old data
- Dual-write: Application writes to both old and new
- Verify: Validate data consistency between old and new
- Switch reads: Point reads to new columns/tables
- Contract: Remove old columns/tables after confidence period
Checklist:
- Migration script is idempotent (re-run safe)
- Rollback script prepared and tested
- Data validation queries defined
- Performance impact assessed (lock duration, table size)
- Backup taken before migration
- Scheduled during low-traffic window
- Monitoring for errors and performance during migration
3. Cloud Migration (Lift & Shift → Re-Platform → Re-Architect)
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.
- 8d ago First seen · 172 lines · 99 tokens per session scan A 910d45169d66
migration-strategy is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 99 tokens to every session and 1,456 once invoked, about $0.0005 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.
Other skills, from other repositories
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
architecture-patterns
Software architecture patterns and best practices.
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
vb6-legacy
Classic VB6 patterns, COM interop, migration strategies.
software-patterns
Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.