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/AgriciDaniel/claude-code-essentials-vs-codeWrote 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/agricidaniel/claude-code-essentials-vs-code/migrate)<a href="https://agentmods.dev/commands/agricidaniel/claude-code-essentials-vs-code/migrate"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/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/agricidaniel/claude-code-essentials-vs-code/migrate"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/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.00005 | $0.00136 |
| Opus 5.5 | $0.00002 | $0.00054 |
| Sonnet 5.5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 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.
What it actually says
Create migration plan for: $ARGUMENTS
Steps:
- Document current state and versions
- Identify breaking changes in target version
- Create step-by-step migration checklist
- Propose codemods if applicable; do not write or execute them
- Plan incremental dependency updates
- Identify tests that would need updates for new APIs
- Create rollback plan
- Document post-migration verification steps
Output as checklist with estimated effort per step. Flag any high-risk changes that need careful review. This command is planning only. Do not edit files, run migrations, or change dependencies.
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 Changed · +1 lines 7f0bcad3814f
- 1mo ago First seen · 18 lines · 5 tokens per session scan A 1424b611f739
migrate is a command published in the GitHub repository AgriciDaniel/claude-code-essentials-vs-code (64 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 136 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-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
ace:execute-plan
Execute current PLAN.md with parallel Team Leads.
ace:validate-zones
Check for zone conflicts in project-types.json.
ace:consider-issues
Review deferred issues for potential inclusion.
ace:validate-plan
Verify PLAN.md structure before execution.
ace:recover-execution
Resume from mid-plan execution failures.