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/iress/design-system/version-migrationnpx skills add iress/design-system --skill version-migrationgit clone --depth 1 https://github.com/iress/design-systemWhat 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.00095 | $0.02683 |
| Opus 5 | $0.00048 | $0.01341 |
| Sonnet 5 | $0.00019 | $0.00537 |
| Haiku 4.5 | $0.00010 | $0.00268 |
Grade A, and why
version-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 2d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: IDS Version Migration
When to Use
- Migrating from IDS v5 (or v4) to IDS v6
- Migrating from OUI (
@iress/oui) to IDS v6 - Updating imports from
@iress/components-reactto@iress-oss/ids-components - Converting Formik forms to React Hook Form via
IressForm/IressFormField - Updating test files that use IDS v4 test utilities
- Reviewing migration PRs for correctness
Decision Table: Which Migration Path?
| Current stack | Migration path | Complexity | Reference |
|---|---|---|---|
| OUI only | OUI→v6 guide | High (form architecture change) | prop-renames.md |
| IDS v4 only | v4→v6 guide | Medium (form architecture change) | prop-renames.md |
| IDS v5 only | v5→v6 guide | Low–Medium | v5-to-v6-migration.md |
| OUI + IDS v4 | Both OUI→v6 and v4→v6 guides | High (form architecture change) | prop-renames.md |
| OUI + IDS v5 | OUI→v6 guide + v5→v6 for IDS changes | High (form architecture change) | v5-to-v6-migration.md |
Full interactive guides with diff viewers are available in Storybook:
Pre-Migration Assessment
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/common-gotchas.md 12 KB
- references/component-renames.md 10 KB
- references/form-migration.md 4.1 KB
- references/prop-renames.md 25 KB
- references/styling-migration.md 1.8 KB
- references/testing-migration.md 5.1 KB
- references/v5-to-v6-migration.md 13 KB
- references/visual-regression-testing.md 5.8 KB
- scripts/audit-components.sh 2.3 KB runs code
- scripts/detect-version.sh 2.2 KB runs code
- scripts/find-deprecated-props.sh 2.7 KB runs code
- scripts/find-formik.sh 2.1 KB runs code
- scripts/find-test-utils.sh 3.1 KB runs code
- scripts/README.md 2.3 KB
- scripts/setup-playwright-vrt.sh 8.3 KB runs code
- scripts/validate-migration.sh 3.7 KB runs code
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.
- 2d ago First seen · 237 lines · 95 tokens per session scan A c34bde14ff28
version-migration is a skill published in the GitHub repository iress/design-system (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 95 tokens to every session and 2,683 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…