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/ci-runners/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/ci-runners)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/ci-runners"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/ci-runners/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/ci-runners"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/ci-runners.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.00843 |
| Opus 5.5 | $0.00019 | $0.00337 |
| Sonnet 5.5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
ci-runners 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Runners
🚫 Deprecated runners
Do not add new usages of these labels. When touching a job that already uses one, offer to migrate it.
ledger-live-mediumledger-live-4xlargeledger-live-linux-8CPU-32RAMledger-live-linux-16CPU-64RAMledger-live-linux-e2e-8CPU-32RAMledger-live-linux-e2e-speculos-32CPU-128RAM
Exception: Android emulator jobs. The emulator needs /dev/kvm, which the runners below don't have (see Gotchas). Android E2E jobs in test-mobile-e2e-reusable.yml run on ledger-wallet-8cpu-github-public-cached, a GitHub larger runner on the ledger-wallet-android-e2e custom image (built in LedgerHQ/ledger-wallet-runners), which holds the toolchain and the E2E AVD. Use it only for jobs that run the emulator.
✅ Allowed runners
| Size | Cached (default) | Uncached (release) |
|---|---|---|
| 1 CPU | ledger-wallet-1cpu-aws-public-cached |
ledger-wallet-1cpu-aws-public |
| 2 CPU | ledger-wallet-2cpu-aws-public-cached |
ledger-wallet-2cpu-aws-public |
| 4 CPU | ledger-wallet-4cpu-aws-public-cached |
ledger-wallet-4cpu-aws-public |
| 8 CPU | ledger-wallet-8cpu-aws-public-cached |
ledger-wallet-8cpu-aws-public |
| 16 CPU | ledger-wallet-16cpu-aws-public-cached |
ledger-wallet-16cpu-aws-public |
ledger-wallet-4cpu-aws-public-docker is the 4 CPU runner for jobs that need a Docker daemon.
Memory is 4 GiB per CPU (e.g. 4cpu = 16 GiB, 8cpu = 32 GiB).
Cached vs uncached
- Default to the
-cachedvariant. - Use the uncached variant for the release process:
release-*.ymlworkflows and jobs that run onmain,releaseorhotfix. Release builds must start from a clean state.
Picking a runner
Never pick silently. Ask the user to choose from the allowed list, with a recommendation:
- Cached or uncached, from the rule above.
- Size from the job's needs. When replacing a deprecated runner, start from the same CPU count (e.g.
ledger-live-linux-8CPU-32RAM→ 8 CPU). There is no 32 CPU option: propose 16 CPU and flag the job for benchmarking. -dockeronly if the job runs containers.
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.
- 5d ago Changed 76e66bd4b69b
- 7d ago First seen · 55 lines · 47 tokens per session scan A 1af0150fb371
ci-runners is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 843 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-10-22.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
update-github-workflows
Add or change GitHub Actions workflows, CI jobs, triggers, matrices, and shared PHP bootstrap behavior while preserving this repository's prerequisite gates, test setup, and reporting safeguards.
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,"…