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-workflow-refs/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-workflow-refs)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/ci-workflow-refs"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/ci-workflow-refs/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-workflow-refs"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/ci-workflow-refs.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.00088 | $0.00696 |
| Opus 5.5 | $0.00035 | $0.00278 |
| Sonnet 5.5 | $0.00018 | $0.00139 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
ci-workflow-refs 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 6d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Workflow Refs (split brain)
How it runs
- Root workflows (
build-and-test-push.yml,build-and-test-pr.yml,merge-queue.yml,release-*.yml) run from the triggering commit's YAML. - Children are pinned:
uses: LedgerHQ/ledger-live/.github/workflows/<x>-reusable.yml@developandLedgerHQ/ledger-live/tools/actions/...@develop. They always run develop's YAML. - Checkout uses
github.sha(orinputs.ref), so the code,package.jsonscripts and Nx projects come from the caller's branch.
On develop the two match. On release, hotfix, main and PRs targeting them, the code can be weeks or months older than the YAML running against it.
What breaks
A child workflow or action on develop can only rely on what exists on every branch that calls it:
- ❌ A new step running
pnpm <new-script>,nx run <new-project>:<target>or a new file path. It fails on release/hotfix, where the script or project doesn't exist yet. - ❌ A new required input on a reusable workflow. Older root workflows don't pass it.
- ❌ Removing or renaming an input or output. Older callers still pass or read it.
- ❌ Changing a composite action's inputs in a way older callers can't satisfy.
Release and hotfix pipelines are the worst place to find this out.
Do this instead
- Prefer
pnpm exec nx run-many -t <target> -p <project>. It is a no-op when the project is absent (seetest-boundaries-reusable.yml). Leave a comment saying why. - Guard steps on presence, e.g.
if: hashFiles('path/to/new/config') != '', or check in the script before running it. - Give new inputs a
defaultand keep them optional. Deprecate inputs before removing them, and remove them only after release and hotfix have caught up. - To make a new check mandatory everywhere, land the code first, then wire it into the root workflow (which runs at the commit) rather than the
@developchild. Or wait until the change has reachedmainbefore you make the child depend on it. - Composite actions are local to the repo, but
@developpins them the same way, so the same rules apply.
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.
- 6d ago First seen · 40 lines · 88 tokens per session scan A b511670d71fd
ci-workflow-refs is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 696 once invoked, about $0.0004 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-23.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
xberg-release
Xberg release on top of the shared release-workflow: task version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.