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/testingnpx skills add LedgerHQ/ledger-live --skill testinggit 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.00066 | $0.01696 |
| Opus 5 | $0.00033 | $0.00848 |
| Sonnet 5 | $0.00013 | $0.00339 |
| Haiku 4.5 | $0.00007 | $0.00170 |
Grade A, and why
testing 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ledger Wallet Testing Skill
Jest + MSW + React Testing Library (Desktop) / React Native Testing Library (Mobile) ❌ E2E tests → Use
e2eskill
Golden Rules
toBeVisible()overtoBeInTheDocument()— Always.toBeInTheDocumentonly checks DOM presence; elements can be hidden. UsetoBeInTheDocumentonly when testing explicitly hidden elements.- Search before you create — Before writing any mock, fixture, or helper,
rgthe codebase. If it exists, import it. If your new mock is reusable (2+ files), put it in a shared location. - Mock external deps only — Never mock child components. Test integration.
- One behavior per test — Name:
it("should <behavior> when <condition>"). - Query priority:
getByRole>getByLabelText>getByText>getByTestId(last resort). - Feature flags via store, never mocked — Use
overriddenFeatureFlagsininitialState.settings. - Use existing factories —
genAccount()from@ledgerhq/ledger-wallet-framework/mocks/account,getCryptoCurrencyById()from@ledgerhq/live-common/currencies. Never recreate account/currency data from scratch.
Quick Reference
pnpm test:jest "filename" # Run specific file
pnpm test:jest # Run all tests
pnpm test:jest --coverage # Coverage report
# Coin modules (libs/coin-modules)
pnpm coin:<name> test # Unit tests
pnpm coin:<name> test "filename" # Specific file
pnpm coin:<name> test-integ # Integration tests (slow)
| Platform | Render Import | MSW Server |
|---|---|---|
| Desktop | tests/testSetup |
tests/server.ts |
| Mobile | @tests/test-renderer |
__tests__/server.ts |
Test Template
import { render, screen, waitFor } from "tests/testSetup";
import { server } from "tests/server";
import { http, HttpResponse } from "msw";
jest.mock("@ledgerhq/live-common/someService");
describe("MyComponent", () => {
beforeEach(() => jest.clearAllMocks());
it("should render title", () => {
render(<MyComponent title="Test" />);
expect(screen.getByText("Test")).toBeVisible();
});
it("should call onClick when button pressed", async () => {
const onClick = jest.fn();
const { user } = render(<MyComponent onClick={onClick} />);
await user.click(screen.getByRole("button"));
expect(onClick).toHaveBeenCalledTimes(1);
});
it("should display fetched data", async () => {
server.use(http.get("/api/data", () => HttpResponse.json({ name: "Bitcoin" })));
render(<MyComponent />);
await waitFor(() => expect(screen.getByText("Bitcoin")).toBeVisible());
});
});
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 · 198 lines · 66 tokens per session scan A f6e7105accdb
testing is a skill published in the GitHub repository LedgerHQ/ledger-live (614 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 1,696 once invoked, about $0.0003 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using package:test. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
myco:runtime-bootstrap-and-test-isolation
Activate this skill when adding a new manager, adding a new tool category, writing or debugging tool unit tests, diagnosing tool-visibility failures, investigating startup performance, or extending/maintaining/debugging the two-tier tool discovery system (toolindex) — even if the user doesn't explicitly ask about the…