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/run-e2e-ci/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/run-e2e-ci)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/run-e2e-ci"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/run-e2e-ci/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/run-e2e-ci"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/run-e2e-ci.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 Rogue Agent · line 19 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00071 | $0.02039 |
| Opus 5.5 | $0.00028 | $0.00816 |
| Sonnet 5.5 | $0.00014 | $0.00408 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
run-e2e-ci 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run E2E / Coin Tester on CI
When: for changes that impact the e2e apps (desktop/mobile/coin logic), once the PR is getting ready for review. Desktop & Mobile E2E only run on a schedule + manual dispatch, so trigger them deliberately. Coin Tester already auto-runs on PRs for affected coins — only dispatch it to force a chain or re-run.
Scope it down first — filtered is the default, full suite is the exception
Always run the smallest subset that covers the change. The full suite is slow, expensive, and competes for shared on-chain accounts, so run it only for genuinely cross-cutting changes — and when you do, say why in the PR comment. Derive the scope from the diff:
| What the diff touches | How to scope |
|---|---|
One coin module (libs/coin-modules/coin-solana) |
test_filter=@solana + Coin Tester chain=solana |
A coin family (**/families/evm) |
test_filter=@family-evm (or @generic-coin-framework) |
A specific spec / flow (swap, subAccount, newSendFlow) |
test_filter with the tag or spec path |
| Everything one team owns | team=<slug> — ANDs with test_filter, Smoke and the device |
| Platform-specific (Android manifest, iOS plist) | narrow Mobile tests_type (Android Only / iOS Only); skip the other surfaces |
| Desktop-only or Mobile-only change | run only that surface; skip the others + Coin Tester |
| Shared / cross-cutting (build tooling, TS upgrade, currency core) | full suite — and add a one-line rationale |
Filter tags: @bitcoin, @family-evm, @solana, @generic-coin-framework, @smoke, … See the test-filter guide for the grammar and the mobile (whole spec files by path/@-tag) vs desktop (test titles) matching difference.
team vs test_filter. test_filter is an OR over its patterns; the team dropdown is an AND that narrows the run to one team's specs. Combine them: team=bst + test_filter=@bitcoin runs only the bitcoin specs BST owns. Slugs: bst, buy-and-sell, coin-integration, earn, engagement, swap, wallet-xp (all is the default and changes nothing). List them with their spec counts:
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.
- 1mo ago Changed · +29 lines df8d52298998
- 2mo ago First seen · 68 lines · 71 tokens per session scan A 7bf51fa8c05d
run-e2e-ci is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 2,039 once invoked, about $0.0003 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
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
testing-and-ci
Choose and run unit, E2E, Caddyfile fixture, automation, and CI checks for caddy-security. Use for coverage requirements, test evidence, failures, and report workflows; official OP conformance remains opt-in.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.