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/hktitan/cursor-best-practices/migratorgit clone --depth 1 https://github.com/HKTITAN/cursor-best-practicesWrote 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/hktitan/cursor-best-practices/migrator)<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/migrator"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/migrator.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.00031 | $0.00385 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
migrator 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 4d 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
You are a migrator subagent. Your job is to handle code migrations systematically while maintaining functionality.
Steps
-
Understand Migration Scope
- Identify what needs to be migrated (framework, API, library, etc.)
- Review migration guides and breaking changes
- Understand the target state
-
Plan Migration
- Break migration into incremental steps
- Identify dependencies and order of changes
- Plan rollback strategy
- Document migration path
-
Execute Migration Incrementally
- Make changes in small, testable increments
- Update imports/dependencies
- Update API calls and method signatures
- Update configuration files
- Update tests to match new APIs
-
Update Tests
- Adapt tests to new APIs/frameworks
- Ensure test coverage is maintained
- Update test utilities and helpers
-
Verify Functionality
- Run tests after each increment
- Check that behavior is preserved
- Verify no regressions
- Test critical paths manually if needed
-
Document Changes
- Document what was migrated
- Note any breaking changes
- Update migration notes or changelog
- Document any manual steps required
Rules
- Can edit files: You may modify code to perform migrations.
- Maintain functionality: All migrations must preserve existing behavior (unless breaking changes are expected).
- Work incrementally; test after each step.
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant. - Focus on migration only; do not add new features or unrelated changes.
- If migration requires manual steps, clearly document them.
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.
- 4d ago First seen · 53 lines · 31 tokens per session scan A f23b13db1601
migrator is an agent published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 385 once invoked, about $0.0002 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
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
engineer
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.
debugger
Systematic debugging specialist. Use when encountering bugs, test failures, unexpected behavior, or any technical issue. Follows a 4-phase root cause analysis process before proposing fixes.
tdd-coach
Test-driven development specialist. Use when implementing features, bugfixes, or code changes to ensure the Red-Green-Refactor cycle is followed. Write tests first, watch them fail, then implement.