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 skills/omnigent-ai/omnigent/migration-guidenpx skills add omnigent-ai/omnigent --skill migration-guidegit clone --depth 1 https://github.com/omnigent-ai/omnigentWrote 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/skills/omnigent-ai/omnigent/migration-guide)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/migration-guide"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/migration-guide.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.00050 | $0.00453 |
| Opus 5 | $0.00025 | $0.00227 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
migration-guide 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
migration-guide — write upgrade steps for a breaking change
Produce a guide that lets a user on the old version land on the new one with the least friction.
Pin down what actually broke
Identify the precise breaking change before writing a word. Get it from the diff and history, not from the description alone:
git diff <old>..<new>on the affected surface, andgh pr view <n>for the PR that introduced it.- Dispatch the researcher (
purpose: explore) to confirm the exact old and new shapes: the old name/signature/default, the new one, and whether a compatibility shim or deprecation window exists.
Never document a rename or signature change from memory — the exact symbols are what users will copy.
Structure
# Migrating to <version>
## What changed
<one paragraph: the change and why, in user terms>
## Upgrade steps
1. <ordered, mechanical steps>
## Before / after
```
# before
...
# after
...
```
## If you can't upgrade yet
<deprecation window, shim, or flag to opt out — if one exists>
Write the steps
- Make each step mechanical and verifiable ("rename
--footo--bar", not "update your flags"). A user should be able to follow it without rereading the whole guide. - Show a minimal, real before/after for each distinct change. Keep examples copy-pasteable.
- State explicitly when there is no automated path and a manual edit is required.
Verify
Route the finished guide through the reviewer (purpose: review). Migration
guides are acted on directly, so a wrong flag name or step is high-cost — the
cross-vendor fact-check is worth it here.
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 · 60 lines · 50 tokens per session scan A 5004d72afa38
migration-guide is a skill published in the GitHub repository omnigent-ai/omnigent (9,658 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 453 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ml-debug
Use when something is failing in ML/AI work — OOM, NaN, divergence, crashes, bad throughput, wrong outputs, dependency conflicts.
ml-plan
Use when the user wants an implementation plan, architecture design, or multi-step ML pipeline — "build X", "implement X", "design X", "set up X".
ml-research
Use when the user wants to understand an ML/AI topic, compare approaches, or survey framework capabilities — "how does X work?", "compare X vs Y".
ml-iterate
Use when the user is stuck, needs ranked next steps, or wants alternatives after initial experiments — "I tried X and got Y, what next?".
using-superml
Use when starting any conversation involving ML/AI — establishes how to use Leeroopedia KB tools and workflow skills.
ml-verify
Use when the user wants to verify code, config, or math before running — or proactively before any expensive training job or deployment.