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-builds/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-builds)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/run-builds"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/run-builds/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-builds"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/run-builds.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01533 |
| Opus 5.5 | $0.00030 | $0.00613 |
| Sonnet 5.5 | $0.00015 | $0.00307 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
run-builds 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce app builds on ledger-live-build CI
When: to produce installable artifacts (desktop installers, APK, iOS) of a ledger-live branch — for QA, manual testing, or sharing a build with reviewers.
These workflows live in LedgerHQ/ledger-live-build, not ledger-live. That changes how you dispatch them vs. run-e2e-ci:
- Target the build repo:
gh workflow run <wf> -R LedgerHQ/ledger-live-build. - The branch you want to build is passed as inputs, not
--ref:-f repo=LedgerHQ/ledger-live -f ref=<branch>. The workflow checks outinputs.reffrominputs.repo.--ref(if given) would select the ledger-live-build ref and should be left at default (main). ghmust run outside the sandbox (dangerouslyDisableSandbox: true).
1. Scope by context — only build what the diff impacts
Builds are slow and expensive (especially desktop = macOS + Linux + Windows). Study the PR diff / branch changes and dispatch only the relevant surfaces:
| Diff touches | Build |
|---|---|
apps/ledger-live-desktop/** |
Desktop |
apps/ledger-live-mobile/** |
Android + iOS |
a package under shared/, domain/, features/, devtools/ |
the app(s) that depend on it, see below |
support/** only (development-only presets) |
nothing |
shared libs (libs/**, e.g. ledger-live-common, coin-modules) impacting both apps |
Desktop + Android + iOS |
If the user explicitly names a platform ("make an APK", "iOS build"), honor that and skip the inference. When in doubt about a shared-lib change, ask which app(s) to build rather than building all three.
Derive the app from a change in the layers with the Nx graph. Pass the changed source files; a package depended on by one app only reaches that app (@features/flow-app-unlock → mobile, @features/platform-app-update → desktop):
FILES=$(gh pr view <pr> -R LedgerHQ/ledger-live --json files \
--jq '[.files[].path | select(test("^(shared|domain|features|devtools)/") and (endswith("package.json") | not))] | join(",")')
pnpm nx show projects --affected --files="$FILES" --json \
| jq -r '.[] | select(. == "ledger-live-desktop" or . == "live-mobile")'
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.
- yesterday Changed · +13 lines 0cf95ef269ef
- 2mo ago First seen · 88 lines · 75 tokens per session scan A 54cc4a06acbf
run-builds is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,533 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
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,"…