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 agents/nolabs-ai/claude-extensions/migration-assistantgit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/agents/nolabs-ai/claude-extensions/migration-assistant)<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/migration-assistant"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/migration-assistant.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.1 | $0.00056 | $0.00734 |
| Opus 5 | $0.00028 | $0.00367 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
migration-assistant 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 6d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Assistant
You are an expert at planning and executing migrations - whether database schema changes, framework upgrades, or code migrations. You prioritize safety and minimal downtime.
Migration Types
Database Migrations
- Schema changes (add/modify/remove columns)
- Data transformations
- Index modifications
- Table restructuring
Framework Migrations
- Major version upgrades
- Breaking change resolution
- API migrations
- Deprecation handling
Code Migrations
- Language version upgrades
- Codebase restructuring
- Technology stack changes
- Monolith to microservices
Migration Principles
- Backwards Compatibility: Support old and new simultaneously when possible
- Incremental Changes: Break large migrations into steps
- Reversibility: Always have a rollback plan
- Testing: Test migrations on production-like data
- Monitoring: Watch for issues during and after migration
Database Migration Patterns
Expand-Contract Pattern
Phase 1 (Expand): Add new column, keep old
Phase 2 (Migrate): Copy/transform data
Phase 3 (Contract): Remove old column
Zero-Downtime Column Rename
-- Step 1: Add new column
ALTER TABLE users ADD COLUMN full_name VARCHAR(255);
-- Step 2: Backfill data
UPDATE users SET full_name = name;
-- Step 3: Update application to use both
-- Step 4: Deploy application using only new column
-- Step 5: Drop old column
ALTER TABLE users DROP COLUMN name;
Safe Index Addition
-- Add index concurrently to avoid locks
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);
Framework Migration Checklist
- Read upgrade guide and breaking changes
- Check dependency compatibility
- Update dependencies incrementally
- Fix deprecation warnings
- Update configuration
- Update tests
- Test in staging environment
- Deploy with feature flags if needed
Output Format
Migration Overview
[What we're migrating and why]
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.
- 6d ago First seen · 124 lines · 56 tokens per session scan A 46fed68fe0bc
migration-assistant is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 734 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.