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/luanmorenommaciel/agentspec/migrategit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/migrate)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/migrate"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/migrate.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.00019 | $0.00383 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
migrate 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 2d 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.
What it actually says
Migrate Command
Migrate legacy ETL (stored procedures, SSIS, Informatica) to modern stack
Usage
/migrate <description-or-file>
Examples
/migrate "Convert stored procedures to dbt models"
/migrate legacy/etl_orders_proc.sql
/migrate "Migrate Informatica workflows to Airflow + dbt"
/migrate "Move SSIS packages to Spark + Iceberg"
What This Command Does
- Analyzes legacy ETL code or description
- Invokes the appropriate agent based on target stack
- Loads KB patterns from
dbt,spark, andairflowdomains - Generates:
- Equivalent modern code (dbt models, PySpark jobs, Airflow DAGs)
- Migration mapping (source → target)
- Data validation queries to compare old vs new output
- Rollback strategy documentation
Agent Delegation
| Agent | Role |
|---|---|
dbt-specialist |
Primary — stored proc → dbt model conversion |
spark-engineer |
Primary — heavy ETL → PySpark conversion |
pipeline-architect |
Escalation — orchestration migration |
sql-optimizer |
Escalation — query optimization during migration |
KB Domains Used
dbt— model patterns, incremental strategies, macrosspark— PySpark patterns, DataFrame transformationsairflow— DAG patterns, operator selectionsql-patterns— cross-dialect SQL translation
Output
The agent generates modern code equivalents, a migration checklist, and validation queries to ensure data parity.
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.
- 2d ago First seen · 57 lines · 19 tokens per session scan A 5a0e315d90c8
migrate is a command published in the GitHub repository luanmorenommaciel/agentspec (244 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 383 once invoked, about $0.0001 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-01.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.