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.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/instructions/ledgerhq/ledger-live/agents-md)<a href="https://agentmods.dev/instructions/ledgerhq/ledger-live/agents-md"><img src="https://agentmods.dev/badge/instructions/ledgerhq/ledger-live/agents-md.svg" alt="Measured on agentmods" 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.00483 | $0.00483 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
ledger-live AGENTS.md 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 3d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Overview
"Ledger Wallet" (formerly "ledger-live") is a crypto wallet. This pnpm and Nx monorepo contains multiple frontend apps and over 150 library packages. See the root README for an overview.
We are working towards consistency across all those packages but each workspace has it's own details. Read local README files relevant to where you are working.
Where to add new code
When creating a new package, follow docs/new-library.md guidelines.
Repo Commands
Prefer commands given in local README files. For example appls like Ledger Wallet Desktop and Ledger Wallet Mobile have very specific commands for setup, dev and build commands.
For general test, build and check recipes see /docs/repo-commands.md, which also contains notes on Nx, filtering and aliases.
External Work Links
When a task includes Jira or Confluence links, use Atlassian MCP to fetch and read the referenced ticket or page by default before summarizing, planning, or implementing.
When a task involves GitHub — pull requests, issues, CI checks, or releases — use the gh CLI by default.
Validate Before Finishing
Always follow the validate-before-finishing instructions before completing code changes.
Keep the external services catalog up to date
- /docs/services.md lists every external service the apps contact (domain, how it's managed, scope/team).
- When you add, remove, or change a service — a new entry in
libs/env/src/env.ts, a hardcoded endpoint, a coin/family config change, or a new SDK dependency that phones home — update the matching table indocs/services.md.
Read READMEs for packages where you're working
See examples:
- Entity packages (
domain/entity/): readdomain/entity/README.md - API packages (
domain/api/): readdomain/api/README.md - Shared packages (
shared/**): readshared/README.md - Support packages (
support/**): readsupport/README.md
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.
- 3d ago First seen · 42 lines · 483 tokens per session scan A 78e991a18211
ledger-live AGENTS.md is an instructions file published in the GitHub repository LedgerHQ/ledger-live (616 stars, last pushed yesterday), licensed MIT. It adds 483 tokens to every session, about $0.0024 per session on Opus 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-09-03.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.