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/docs-update-or-create/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/docs-update-or-create)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/docs-update-or-create"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/docs-update-or-create.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.00043 | $0.00656 |
| Opus 5 | $0.00022 | $0.00328 |
| Sonnet 5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
docs-update-or-create 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or Update Docs
Create minimal docs, avoid duplication and make content discoverable. Treat docs for both human and AI agents together. Follow our principles of progressive disclosure, locality and canonicalization.
📝 Process to follow
- Understand the topic of knowledge and its purpose
- Gather existing knowledge on that topic
- Agree on the best format and location for it to live
- Write/update the files, inline with what's agreed
- Validate the results and refine as necessary
📜 Guidelines
These guidelines define some boundaries within which to operate. They do not dictate everything. Follow them, but also use judgement and creativity to find the best way to document knowledge in each case.
❌ BAD:
- Avoid long files containing multiple levels of details
- Avoid overloading context with rarely used knowledge
- Avoid duplicating knowledge in multiple files
- Avoid documenting community-obvious knowledge
- Avoid preserving old structure for its own sake
✅ GOOD:
- Add docs that measurably improve agent performance
- Do document repeatable workflows, commands and behaviours
- Capture what is peculiar to this repo, domain, or team
- Only add docs that solve real problems
- Delete files that have no unique value after changes
- Use emojis, checkboxes and formatting sparingly to make docs more appealing
Keep it short
- Keep it short and direct. Treat 100 lines as a target (not a hard limit)
- Keep each file at one level of detail.
- Link to narrower docs when detail must branch.
- Use short inline examples when they replace explanation.
- Link longer examples instead of embedding them.
Use frontmatter
- Skill and agent definitions should use frontmatter to be discoverable by tools.
- Frontmatter for READMEs is optional. If it's useful for you, include it
- Tool-discoverable docs and skills should have
nameanddescription - Add
allowed-tools, orcompatibilityonly when they help. - Use
disable-model-invocation: truefor user-invoked skills (commands) - Use
user-invocable: falsefor agent-only skills
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.
- 7d ago First seen · 84 lines · 43 tokens per session scan A 5e63c32491ed
docs-update-or-create is a skill published in the GitHub repository LedgerHQ/ledger-live (616 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 656 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…