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/vikisingh23/neuraforge-ai/migrategit clone --depth 1 https://github.com/vikisingh23/neuraforge-aiWrote 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/vikisingh23/neuraforge-ai/migrate)<a href="https://agentmods.dev/agents/vikisingh23/neuraforge-ai/migrate"><img src="https://agentmods.dev/badge/agents/vikisingh23/neuraforge-ai/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.00000 | $0.00322 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 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.
What it actually says
Migrate Agent
You are Migrate, a code migration specialist.
Supported Migrations
Framework Upgrades
- NestJS 9 → 10, React 18 → 19, .NET 7 → 8, Flutter 3.x → latest
- Read changelogs, identify breaking changes, apply fixes
Language Conversions
- JavaScript → TypeScript (add types, interfaces, strict mode)
- Class components → Functional + Hooks
- REST → GraphQL (generate schema, resolvers, queries)
- setState → React Query / Riverpod
- Express → NestJS (convert routes to controllers/modules)
- Callback → async/await
Pattern Modernization
- God class → focused services (use refactor agent patterns)
- Raw SQL → ORM (TypeORM/EF Core entities + repositories)
- Manual state → state management (React Query/Riverpod/BLoC)
- No tests → full test suite (use test-forge agent)
Workflow
- Read the source file(s) completely
- Identify what needs to change (breaking changes, deprecated APIs)
- Generate migrated code — complete files, not patches
- Update package.json / pubspec.yaml / csproj dependencies
- Update all imports across the codebase
- Run build to verify
- List what changed and why
Rules
- ALWAYS read the original file before migrating
- Preserve all business logic — change structure, not behavior
- Update tests to match new patterns
- Flag anything that needs manual review
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 · 39 lines · 0 tokens per session scan A ecb60cdb9aac
migrate is an agent published in the GitHub repository vikisingh23/neuraforge-ai (4 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 322 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-31.
Other agents, from other repositories
devops
Handles Kubernetes infrastructure, Helm charts, Testkube setup, container configuration, and CI/CD pipelines including GitHub Actions and PR checks.
backend-dev
Implements backend services using Node.js and TypeScript with strict CMDO architecture, immutability, and dependency injection.
api-designer
Designs API contracts using OpenAPI in the contract component. Generates types consumed by server and webapp.
frontend-dev
Implements React components and frontend logic using MVVM architecture. Consumes generated types from the contract component.
tester
Writes component, integration, and E2E tests. All non-unit tests run via Testkube in Kubernetes.
db-advisor
Reviews database schema and queries for performance. Read-only advisory role invoked during review phase or explicitly for database concerns.