ledger-live: Agent for Claude Code

.agents/agents/ci-watcher.md

ci-watcher is an agent for Claude Code from LedgerHQ/ledger-live. It costs 40 tokens per session (185 once invoked), scanned A, original, MIT.

An agent that watches GitHub Actions, a service that runs automated checks for a code branch, and reports whether the latest run passed or failed.

In plain words
What is it for?
Use it while waiting for branch checks, after a failure, or proactively during development to get the run details and a concise failure summary.
Why use it?
It removes the need to repeatedly check CI status and helps you locate the relevant logs when a check fails.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: installed under .agents/ (shared by several agents).

This is LedgerHQ/ledger-live's own configuration. It tells Claude Code how to work on ledger-live itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ledger-live configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/agents/ci-watcher.md
Clone the repo
git clone --depth 1 https://github.com/LedgerHQ/ledger-live

Made for: Claude Code.

Wrote 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.

agentmods badge for ci-watcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/ledgerhq/ledger-live/ci-watcher/github.svg)](https://agentmods.dev/agents/ledgerhq/ledger-live/ci-watcher)
Your own site
<a href="https://agentmods.dev/agents/ledgerhq/ledger-live/ci-watcher"><img src="https://agentmods.dev/badge/agents/ledgerhq/ledger-live/ci-watcher/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.

agentmods 80×15 button for ci-watcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/ledgerhq/ledger-live/ci-watcher"><img src="https://agentmods.dev/badge/agents/ledgerhq/ledger-live/ci-watcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 185 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00185
Opus 5.5 $0.00016 $0.00074
Sonnet 5.5 $0.00008 $0.00037
Haiku 4.5 $0.00004 $0.00018

Measured yesterday against content hash 7db306645ca9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-watcher 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.

.agents/agents/ci-watcher.md · 25 lines

What it actually says

CI watcher

CI monitoring specialist for GitHub Actions.

Trigger

Use when waiting for CI results, CI has failed, or when proactively monitoring branch CI.

Workflow

  1. Determine current branch: git branch --show-current
  2. Find latest run for that branch: gh run list --branch <branch> --limit 1
  3. Watch to completion: gh run watch <run-id> --exit-status
  4. If failed, fetch failed logs: gh run view <run-id> --log-failed

Output

  • CI status (passed/failed)
  • Workflow/run metadata
  • If failed: concise failure excerpt and likely next step
Changes

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.

  1. yesterday Changed · -2 lines 7db306645ca9
  2. 2mo ago First seen · 27 lines · 40 tokens per session scan A cd668f2f6082

Subscribe to this mod's changes

ci-watcher is an agent published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 185 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-08-30.