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/CrashBytes/claude-role-skillsWrote 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/crashbytes/claude-role-skills/migrate)<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/migrate"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/migrate/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/commands/crashbytes/claude-role-skills/migrate"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/migrate.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.00006 | $0.00423 |
| Opus 5.5 | $0.00002 | $0.00169 |
| Sonnet 5.5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 2mo 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
Migration Assessment
Assess a system for migration readiness and generate a migration plan.
Arguments
Migration scope: $ARGUMENTS
Workflow
-
Assess current state
- If a codebase is available, scan for: languages, frameworks, dependencies, database types
- Identify: code complexity, test coverage, documentation quality
- Map external integrations and data flows
- Estimate technical debt level
-
Classify with the 7 Rs For each component, recommend one of:
- Retain: Keep as-is (low risk, low value to migrate)
- Retire: Decommission (no longer needed)
- Rehost: Lift-and-shift (move without changes)
- Replatform: Lift-and-reshape (minor optimizations)
- Repurchase: Replace with SaaS/COTS
- Refactor: Re-architect for the target platform
- Reimagine: Build from scratch
-
Identify risks
- Data migration complexity (schema differences, data volume, transformation needs)
- Integration points that will break
- Feature parity gaps
- Team skill gaps
- Downtime requirements and business constraints
-
Design migration strategy
- Recommend: Big Bang vs Strangler Fig vs Parallel Run
- Phase breakdown with dependencies
- Data migration approach (ETL, CDC, dual-write)
- Rollback plan for each phase
- Testing strategy (shadow traffic, parallel validation)
-
Output
- Current state assessment
- Component classification (7 Rs)
- Risk register with mitigation strategies
- Phased migration plan with timeline
- Go/no-go checklist for each phase
- Resource and skill requirements
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.
- 2mo ago First seen · 54 lines · 6 tokens per session scan A bc0a5fcdc72e
migrate is a command published in the GitHub repository CrashBytes/claude-role-skills (8 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 423 once invoked, about $0.0000 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.
migrate compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| migrateCrashBytes/claude-role-skills | Command | 8 | 8mo ago | Apache-2.0 | A | 6 | Claude Code |
| launch-meta-campaignmarkifact/markifact-mcp | Command | 59 | yesterday | MIT | A | 36 | Claude Code, Cursor |
| negative-keyword-sweepmarkifact/markifact-mcp | Command | 59 | yesterday | MIT | A | 50 | Claude Code, Cursor |
| meetingssystemoperators/claude-plugins | Command | 6 | today | MIT | A | 6 | Claude Code |
| notessystemoperators/claude-plugins | Command | 6 | today | MIT | A | 6 | Claude Code |
| duck-offcentsandcode/rubber-duck | Command | 15 | 2mo ago | MIT | A | 8 | Claude Code |
| triagenunoamorim99/agile-ledger | Command | 1 | 20d ago | MIT | A | 25 | Claude Code |