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/ledgerhq/ledger-live/wire-devtoolnpx skills add LedgerHQ/ledger-live --skill wire-devtoolgit clone --depth 1 https://github.com/LedgerHQ/ledger-liveWhat 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.00027 | $0.01018 |
| Opus 5 | $0.00014 | $0.00509 |
| Sonnet 5 | $0.00005 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
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 3d 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 — 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, 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.
- 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>Props 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>Props.ts — a hook that reads from the host's state and returns the tool's props type. Then re-export it from devtools/bindings/src/index.ts.
// devtools/bindings/src/useMyToolProps.ts
import type { MyToolProps } from "@devtools/my-tool";
export function useMyToolProps(): MyToolProps {
return {
// TODO: replace with real selectors
property: undefined,
};
}
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.
- 3d 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 (614 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,018 once invoked, about $0.0001 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-30.
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…