who-owns

who-owns is a command for Claude Code from cognitx-leyton/codegraph. It costs 16 tokens per session (670 once invoked), scanned A, original, Apache-2.0.

A file-ownership lookup command. It shows who last changed a file, its main contributors, and the teams listed as responsible in the CODEOWNERS file.

In plain words
What is it for?
Use it with a repository-relative file path. It reports the latest author, contribution history, and matching CODEOWNERS teams from the project's code graph.
Why use it?
It gives developers a quick way to find the people and teams familiar with a file. This makes review and questions easier to direct to the right owners.

Command for Claude Code

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 commands/cognitx-leyton/codegraph/who-owns
Clone the repo
git clone --depth 1 https://github.com/cognitx-leyton/codegraph

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 who-owns

README.md
[![agentmods](https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/who-owns.svg)](https://agentmods.dev/commands/cognitx-leyton/codegraph/who-owns)
Your own site
<a href="https://agentmods.dev/commands/cognitx-leyton/codegraph/who-owns"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/who-owns.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 670 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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00670
Opus 5 $0.00008 $0.00335
Sonnet 5 $0.00003 $0.00134
Haiku 4.5 $0.00002 $0.00067

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

Security

Grade A, and why

who-owns 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 5d 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.

.claude/commands/who-owns.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Usage

/who-owns <path>

Path must match :File.path exactly — repo-root-relative with forward slashes (e.g. codegraph/codegraph/loader.py, not absolute, not with a leading ./).

Joins three ownership edges written by the Phase-7 ownership pass:

Edge Source Columns
LAST_MODIFIED_BY most-recent commit from git log author name, email, timestamp
CONTRIBUTED_BY all authors for the file, with commit counts roll-up of top 5
OWNED_BY CODEOWNERS file team name(s)

What this does

codegraph query "
MATCH (f:File {path: '$ARGUMENTS'})
OPTIONAL MATCH (f)-[lm:LAST_MODIFIED_BY]->(last:Author)
OPTIONAL MATCH (f)-[c:CONTRIBUTED_BY]->(co:Author)
OPTIONAL MATCH (f)-[:OWNED_BY]->(t:Team)
WITH f, last, lm, t, co, c
ORDER BY c.commits DESC
WITH f,
     last,
     lm,
     collect(DISTINCT t.name) AS teams,
     collect({author: co.name, email: co.email, commits: c.commits})[..5] AS top_contributors
RETURN f.path AS file,
       last.name AS last_modified_by,
       last.email AS last_email,
       lm.at AS last_modified_at,
       teams,
       top_contributors
"

Caveats

  • Requires ownership indexing. /graph-refresh runs with --skip-ownership by default (it's ~30s slower with it). If last_modified_by comes back null and top_contributors is [{author: null, ...}], re-index without the flag:
    codegraph index . -p codegraph/codegraph -p codegraph/tests --no-wipe
    
  • CODEOWNERS must be present. If the repo has no CODEOWNERS file (or .github/CODEOWNERS / docs/CODEOWNERS), the teams column will be empty. That's not a bug — it's the absence of team-level ownership metadata.
  • Path has to match exactly. Use /graph "MATCH (f:File) WHERE f.path CONTAINS 'loader' RETURN f.path" if you're not sure of the stored path.
  • Author email is the join key (CREATE CONSTRAINT author_email ... UNIQUE). If the same person commits under multiple emails, they appear as separate authors.

Read the full file on GitHub · 59 lines

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. 5d ago First seen · 59 lines · 16 tokens per session scan A 8b2dae2cf39b

Subscribe to this mod's changes

who-owns is a command published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 670 once invoked, about $0.0001 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.