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/test-coverage/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/test-coverage)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/test-coverage"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/test-coverage/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/test-coverage"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/test-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 19 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00021 | $0.00736 |
| Opus 5.5 | $0.00008 | $0.00294 |
| Sonnet 5.5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
test-coverage 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 2mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage
Increase test coverage to 90% on a target zone with iterative writing and refactoring.
Prompt Variables
$TARGET_ZONE
Directory path or Jira ticket URL for the zone to cover (e.g.,
src/mvvm/features/Accounts/orhttps://ledgerhq.atlassian.net/browse/LIVE-1234)
Instructions
Follow all conventions from the testing skill (.agents/skills/testing/SKILL.md).
Delegate test execution to the test-runner subagent throughout.
Step 1: Scope and Analyze
- If
$TARGET_ZONEis a Jira URL, fetch the ticket via Atlassian MCP and extract affected files. - Use
code-explorersubagent to analyze the zone: trace execution paths, map dependencies, and identify branching logic worth testing. - Measure current coverage:
pnpm <mobile|desktop> test:jest --coverage \ --collectCoverageFrom='<zone-glob>' \ --coverageReporters=text-summary - From the
code-exploreranalysis, build the list of files to test. Skip type definitions, barrel re-exports, and thin wrappers with no branching. - For each remaining file, ask:
- Does it contain branching logic, state transitions, or side effects?
- Would a regression break user-facing behavior?
- Is it already covered indirectly by a parent test? If all answers are no, skip.
Step 2: Write Tests
Order: pure utils -> hooks -> viewModels -> components with side effects.
For each file:
- Search existing mocks/fixtures/factories before creating new ones (see testing skill).
- Write tests following all testing skill conventions.
- Run tests via
test-runner. Fix failures before moving to the next file.
Loop until coverage >= 90%.
Step 3: Refactoring Loop
Three sequential passes. After each pass, run tests via test-runner -- they must still pass before the next pass.
Pass 1 -- Audit mocks
- For every mock (
jest.mock,jest.fn,mockReturnValue,jest.spyOn): is it asserted directly or does it enable a code path whose output is asserted? - Remove any mock that satisfies neither. Simplify over-specified mocks.
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.
- 2mo ago First seen · 80 lines · 21 tokens per session scan A 99e4fce012a6
test-coverage is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 736 once invoked, about $0.0001 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…