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 skills add Chemaclass/agnostic-ai --skill spec-migrationgit clone --depth 1 https://github.com/Chemaclass/agnostic-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/skills/chemaclass/agnostic-ai/spec-migration)<a href="https://agentmods.dev/skills/chemaclass/agnostic-ai/spec-migration"><img src="https://agentmods.dev/badge/skills/chemaclass/agnostic-ai/spec-migration/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/skills/chemaclass/agnostic-ai/spec-migration"><img src="https://agentmods.dev/badge/skills/chemaclass/agnostic-ai/spec-migration.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.00068 | $0.01304 |
| Opus 5.5 | $0.00027 | $0.00522 |
| Sonnet 5.5 | $0.00014 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
spec-migration 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-migration
A spec migration rewrites a user's old spec form into the new one without changing what sync writes. agnostic-ai migrate runs every pending migration from one registry, specMigrations in internal/cli/migrate.go (#1755). Users should never have to rewrite specs by hand after an upgrade.
When a change needs one
Ask this for every change to a spec kind, a frontmatter field, a YAML key, or agnostic-ai.yaml:
| The change | What to ship |
|---|---|
| Renames a field, or adds a new form that some or all entries map to one to one | A migration and a lint warning on the old form; the old form stays accepted |
| Deprecates a form that no entry maps to one to one | No migration: a lint warning that explains the manual rewrite |
| Adds a new optional field | Nothing |
| Rejects specs that used to load, where a rewrite that keeps their meaning makes them load again | A migration, plus a lint warning at least one release before the rejection |
| Changes a form's meaning or default | Not a migration: a behavior change with a CHANGELOG entry and a lint warning at least one release ahead |
| Removes a form | Only in a breaking release, after its migration shipped, no earlier than the migration's issue allows |
| A style preference with no change in meaning or output | Nothing, or a lint note. Never a migration |
While the project is 0.x, a breaking release is a minor release whose CHANGELOG has a breaking section.
Rules
- Output stays the same.
sync, thenmigrate, thensync --checkexits 0 for every target the spec already reached. The only exceptions are the ones the migration's issue names, such as a spec reaching new targets (whichsyncthen lists) or a literal secret becoming a reference. Any other change to a synced file is not a migration. - Old form keeps working until its removal release. That release replaces it with an error that names the migration to run with the last version that has it. The migration and its fixture stay until then.
- Safe to run twice, and stateless. A migration detects its own old form. Running it twice changes nothing. The release it records is metadata only.
- Map one to one or skip. Entries that do not map stay as written with a one-line reason that
migratereports. A spec that sets both the old and the new form is a skip, never a merge. - Touch only what you own. Edit through the shared editor in
internal/cli/migrate_yaml.go:rewriteTopLevelYAMLKeysfor a YAML spec,rewriteFrontmatterKeysfor Markdown frontmatter. Comments, key order, quoting, and bodies stay as written. The registry writes atomically and keeps the file mode. - Never expose a secret. Diffs, skip reasons, and errors show values of
env,headers, URLs, and args as references or<redacted>;redactMigrationLinesdoes this for every migration. A migration never turns a reference into a literal and never moves a value into another file or into the global home. - Stay inside the spec roots. The registry resolves each change's real path. A file outside the project,
local/, or global spec roots, such as a pack or a symlink into one, becomes a skip that names the pack. Skip a pack layer's entry inPlanwithpackSkip. - Import writes the new form. A project that starts after the change never needs the migration.
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.
- 6d ago Changed 53faaaed152a
- 11d ago First seen · 51 lines · 68 tokens per session scan A 1c9a8d2d0771
spec-migration is a skill published in the GitHub repository Chemaclass/agnostic-ai (25 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,304 once invoked, about $0.0003 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-10-05.
Other skills, from other repositories
conductor-setup
Scaffolds the project and sets up the Conductor environment interactively.
conductor-newTrack
Plans a new track, generates spec and plan files, and registers it in the tracks registry.
conductor-review
Reviews a completed track against its plan and guidelines; auto-archives on pass, auto-deletes and restarts on fail.
conductor-status
Displays the current progress of all tracks in the project.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…