Borrowing it
Nothing to install: this file belongs to LedgerHQ/ledger-live. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/skills/legacy-migration/SKILL.mdgit clone --depth 1 https://github.com/LedgerHQ/ledger-liveWrote 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/ledgerhq/ledger-live/legacy-migration)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/legacy-migration"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/legacy-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/ledgerhq/ledger-live/legacy-migration"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/legacy-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.00126 | $0.01640 |
| Opus 5.5 | $0.00050 | $0.00656 |
| Sonnet 5.5 | $0.00025 | $0.00328 |
| Haiku 4.5 | $0.00013 | $0.00164 |
Grade A, and why
legacy-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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy migration
Code leaves libs/ and apps/*/src in three steps: addition, deprecation, deletion. Each step
is its own PR and leaves develop working. structure-flow decides
which layer receives the code; this skill covers how it gets there. The layer model and the status
of each libs/ area live in the architecture guide.
Boundary rules this relies on
shared/,domain/andfeatures/never import alibs/package (scope:libstag), neither as a declared dependency nor as a source import.- Only
apps/imports both sides. Legacy code may consume new code as migration glue, never the reverse. - No new exception.
BOUNDARY_EXCEPTIONSinconstraints.jslists the existing allowances for a new package to depend on a legacy one, each kept only until that legacy package leaves the repo. When a new package needs legacy code, inject it (below); never add an entry. - Never re-export a legacy type from a new-architecture barrel.
pnpm lint:boundaries enforces the import rules: it checks the Nx graph against the layer
constraints, scans source imports under shared/, domain/ and features/ for legacy packages,
and rejects manifests that declare a banned package. Run it before every migration commit.
1. Addition
Build the replacement in the lowest valid layer, with its tests, while the legacy code keeps working. Keep the public names when the new package is a drop-in replacement: callers then switch by changing an import path.
Example: @features/platform-feature-flags was added as a Redux-backed drop-in replacement for the
Context-based hooks of @ledgerhq/live-common/featureFlags (useFeature, useFeatureFlags,
FeatureToggle), reading the slice that @shared/feature-flags owns. No caller moved in that PR.
2. Deprecation
Point every caller at the replacement and stop new ones from appearing:
What ships with it
1 file 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.
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.
- yesterday First seen · 123 lines · 126 tokens per session scan A 17498ae08266
legacy-migration is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 1,640 once invoked, about $0.0005 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-28.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…