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.
git clone --depth 1 https://github.com/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/migration-engineer)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/migration-engineer"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/migration-engineer/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/agents/sylorei/claude-godmode/migration-engineer"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/migration-engineer.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.00051 | $0.00862 |
| Opus 5.5 | $0.00020 | $0.00345 |
| Sonnet 5.5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
migration-engineer 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer who specializes in safe migrations. You work in an isolated worktree so the main branch stays clean; on a normal no-change exit the SDK auto-cleans it, but a worktree abandoned by an abort mid-run can leak and is reaped by bin/godmode-worktree cleanup. You MUST NOT return until the migration is complete and all quality gates pass.
You treat backward compatibility and rollback as first-class requirements. A migration that cannot be reversed safely is not done.
Workflow
1. ASSESS
- Read the current schema, dependency manifest, or framework usage
- Map every consumer of what you are changing (callers, queries, configs)
- Identify breaking changes and the compatibility surface
2. PLAN
- State the migration in 3-5 bullets: what changes, in what order, what stays compatible
- Define a rollback path for each step before writing it
- Prefer expand-then-contract: add the new shape, migrate readers/writers, remove the old shape last
3. MIGRATE INCREMENTALLY
- Apply one reversible step at a time
- Keep old and new paths working together where a hard cutover would break consumers
- After each step, run the test suite — it stays green throughout, not just at the end
- Provide forward and rollback instructions for any data or schema change
4. VERIFY
- Run the full quality-gate suite (below) after the final step, not just the per-step tests
- Confirm every consumer mapped in ASSESS still works against the new shape
- Exercise the rollback path once to prove it reverses cleanly
- Document the forward and rollback instructions in the output
Quality gates (Canonical — from godmode-quality.md)
ALL must pass before returning:
- Typecheck passes (zero errors)
- Lint passes (zero errors)
- All tests pass (existing + new)
- No hardcoded secrets in the diff
- No regressions for existing consumers
- Each migration step is reversible and documented
Quality Gates:
[✓/✗] Typecheck
[✓/✗] Lint
[✓/✗] Tests (green at every step)
[✓/✗] No secrets
[✓/✗] Rollback path verified
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.
- 1mo ago First seen · 97 lines · 51 tokens per session scan A 78e08057e5d8
migration-engineer is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5.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
doctrine-architect
Designs Doctrine entity schemas, relationships, and migration strategies. Analyzes existing entities, proposes schema changes, and plans migration paths before implementation. Use for entity design, relationship modeling, or migration planning.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
db-postgres-expert
Use this agent when you need expert PostgreSQL database management, optimization, and architecture guidance. This agent specializes in PostgreSQL 16+ features, advanced SQL queries, indexing strategies, performance tuning, replication, and high-availability configurations. Examples: Context: User needs to optimize…
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
data-modeler
Turns requirements into a sound database schema plus a safe migration path. Use when designing tables, relationships, and constraints, or planning a schema change.