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/wire-devtool/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/wire-devtool)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/wire-devtool"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/wire-devtool/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/wire-devtool"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/wire-devtool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01078 |
| Opus 5.5 | $0.00018 | $0.00431 |
| Sonnet 5.5 | $0.00009 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
wire-devtool 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wire Devtool
Reference: devtools/README.md.
Warning: bindings, protocols, registry, relay, shell, transport, transport-panel, and wire are internal platform packages, not tools: do not wire them. feature-flags is an example of a real tool.
1. Identify the tool
- Ask for the tool name if not already provided as an argument or in context.
- If
devtools/<tool-name>/does not exist, stop and tell the user to generate it first:pnpm --filter @devtools/registry add-tool - If it exists, read only
devtools/<tool-name>/src/types.tsto determine whether the tool has props (file present = has props). Do not read anything else.
2. Ask where to wire
AskUserQuestion({
questions: [
{
question: "Which host apps should I wire this tool into?",
header: "Host wiring",
multiSelect: true,
options: [
{ label: "LLD", description: "apps/ledger-live-desktop" },
{ label: "LLM", description: "apps/ledger-live-mobile" },
{ label: "web-tools", description: "apps/web-tools" },
]
}
]
})
Stop here if the user selects none.
If the tool has props, check whether devtools/bindings/src/use<ToolName>ToolProps.ts already exists (a few older hooks are named use<ToolName>DevToolProps.ts, e.g. useEnvDevToolProps.ts).
- If it exists, skip to step 4 and use it directly.
- If it does not exist, ask:
AskUserQuestion({
questions: [
{
question: "Should I create a bindings hook for this tool?",
header: "Bindings",
multiSelect: false,
options: [
{ label: "Yes", description: "Create use<ToolName>ToolProps in @devtools/bindings and wire it into selected hosts." },
{ label: "No", description: "Skip bindings — wire with config: undefined for now." },
]
}
]
})
3. Create bindings (if requested)
Create devtools/bindings/src/use<ToolName>ToolProps.ts, a hook that reads from the host's state and returns the tool's props type (e.g. useFeatureFlagsToolProps.ts). Then re-export it from devtools/bindings/src/index.ts.
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 Changed · +19 tokens per session 38399d17334c
- 2mo ago First seen · 115 lines · 27 tokens per session scan A b628f09bfcc8
wire-devtool is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,078 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-08-30.
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…