What is codeownership?

A guide for maintaining CODEOWNERS files, which assign parts of a codebase to the teams responsible for reviewing them.

Use it to organize team-specific directories, update ownership records, split files touched by too many teams, and identify the responsible team for changed files.

It keeps ownership clear and helps avoid review bottlenecks when files or directories involve multiple teams.

codeownership — Skill for Claude Code and Codex by LedgerHQ: A guide for maintaining CODEOWNERS files, which assign parts…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/ledgerhq/ledger-live/codeownership

Any agent

npx skills add LedgerHQ/ledger-live --skill codeownership

Clone the repo

git clone --depth 1 https://github.com/LedgerHQ/ledger-live

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ledgerhq/ledger-live/codeownership.svg)](https://agentmods.dev/skills/ledgerhq/ledger-live/codeownership)

Your own site

<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/codeownership"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/codeownership.svg" alt="Measured on agentmods" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 530 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00051	$0.00530
Opus 5	$0.00026	$0.00265
Sonnet 5	$0.00010	$0.00106
Haiku 4.5	$0.00005	$0.00053

Measured 4d ago against content hash 4b1d508f6408, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codeownership 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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (resolve-codeowners.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/codeownership/SKILL.md · 63 lines

What it actually says

Codeownership

Why

To reduce cross-team review bottlenecks

What

Make ownership of team specific directories clear
Organise some directories into team-specific sub-directories
Maintain CODEOWNERS files when team specific directories are added or removed
Split monolithic files or folders that have been identified as being touched by too many teams

Resolving ownership for a list of files

Use resolve-codeowners.js to annotate any list of files with their CODEOWNERS team — handy when splitting a large PR by team owner. The script finds ignore in the pnpm virtual store automatically (no extra install).

# From a git diff
git diff --name-only HEAD~1 | node .agents/skills/codeownership/resolve-codeowners.js

# Explicit file list
node .agents/skills/codeownership/resolve-codeowners.js apps/ledger-live-desktop/src/foo.ts libs/env/src/bar.ts

# Override CODEOWNERS location
node .agents/skills/codeownership/resolve-codeowners.js --codeowners /path/to/CODEOWNERS <files...>

Output format (same columns as CODEOWNERS, but resolved to actual files):

apps/ledger-live-desktop/src/main/index.ts  @ledgerhq/platform
apps/ledger-live-desktop/src/renderer/foo.ts  @ledgerhq/wallet-xp
.github/workflows/e2e.yml  @ledgerhq/wallet-ci @ledgerhq/qaa
random/unknown/file.xyz  (no owner)

Semantics: last-rule-wins; ownerless entries appear as (no owner).

Target

Splitting a monolithic file

Split [foo].ts into [foo]/team-[name]/*.ts

Maintaining team specific directories

Example

/shared/feature-flags/src/flags/ contains team-coin-integration, team-engagement, team-live-devices, etc.

CODEOWNERS defines the owner for each of these:

**/team-coin-integration/         @ledgerhq/coin-integration
**/team-engagement/               @ledgerhq/engagement
**/team-live-devices/             @ledgerhq/live-devices

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

resolve-codeowners.js 6.6 KB runs code

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.

4d ago First seen · 63 lines · 51 tokens per session scan A 4b1d508f6408

Subscribe to this mod's changes

codeownership is a skill published in the GitHub repository LedgerHQ/ledger-live (615 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 530 once invoked, about $0.0003 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.

ledger-live ledger-wallet

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens