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/wrap-third-party-libs/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/wrap-third-party-libs)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/wrap-third-party-libs"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/wrap-third-party-libs/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/wrap-third-party-libs"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/wrap-third-party-libs.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.00054 | $0.00791 |
| Opus 5.5 | $0.00022 | $0.00316 |
| Sonnet 5.5 | $0.00011 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
wrap-third-party-libs 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 19d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap third-party libs below the apps
An app's package.json lists workspace packages and the exceptions below (framework singletons, the design system, tooling). A library that serves one capability (QR code, signature check, storage, id generation) belongs to a package below the app, which exposes a small API of our own.
Why
- Every direct app dependency is a potential silent override. The renderer's
resolve.modulesputs the app'snode_modulesfirst, so the app's copy wins over the version a library declared for itself (@noble/curvesv1 forced onto a v2 consumer crashed Desktop at boot). - Desktop and mobile each pick a different lib for the same job (
qrcodevsreact-native-qrcode-svg). One owner gives one behaviour and one test. - Bumping or swapping a lib touches one package, not two apps.
Rule
- Before adding a dependency to
apps/*, look for an existing owner package. If none, create one. - Place the owner in the lowest valid layer of the structure-flow table (
shared,domain,features/platform,features/flow), for example:- business-agnostic (QR code, clipboard, linking, list reorder):
shared/<name>, e.g.@shared/ui-qr-code - capability shared across flows or apps:
features/platform/<name> - used by one flow or one domain: that
features/flowordomainpackage
- business-agnostic (QR code, clipboard, linking, list reorder):
- The package declares the third-party lib in its own
dependencies(catalog:when a catalog entry exists). Apps and other packages import the package by name, never the lib. - The public API hides the lib: no lib types or instances in exports, so the lib can be replaced without touching callers.
- Add a test in the package that exercises the real lib, including the success path.
Examples
Existing app dependencies predate this rule and are migrated over time; do not add new ones.
shared/ui-qr-code(intent of the pattern; its API and placement are still under platform review): ownsqrcode; apps render<QrCode />(Desktop still declaresqrcodeuntil migrated).- #23097:
@noble/curvesand@trust/keytomoved out of Desktop into@features/platform-app-update;sslHelper.verifybecame a wrapper. Precedent for isolating a lib an app used once; the package is Desktop-only today, so it is not a placement model for new packages.
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.
- 19d ago First seen · 45 lines · 54 tokens per session scan A ca2cc857a134
wrap-third-party-libs is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 791 once invoked, about $0.0002 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-10.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
remove
Remove a deployed framework or addon from the current workspace.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.