security-ownership-map

security-ownership-map is a skill for Claude Code, Codex from tercumantanumut/selene. It costs 99 tokens per session (2,109 once invoked), scanned A, a copy of security-ownership-map, MIT.

A method for using Git history to map which people work on which files, with special attention to security-sensitive code.

In plain words
What is it for?
It helps calculate bus factor, identify sensitive-code owners, group files that change together, and export CSV, JSON, or graph data for analysis.
Why use it?
It reveals concentrated knowledge and ownership gaps that can create review or maintenance risks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps calculate bus factor, identify sensitive-code owners, group files that change together, and export CSV, JSON, or graph data for analysis.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tercumantanumut/selene/security-ownership-map
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.

Any agent
npx skills add tercumantanumut/selene --skill security-ownership-map
Clone the repo
git clone --depth 1 https://github.com/tercumantanumut/selene

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.

agentmods badge for security-ownership-map

README.md
[![agentmods](https://agentmods.dev/badge/skills/tercumantanumut/selene/security-ownership-map/github.svg)](https://agentmods.dev/skills/tercumantanumut/selene/security-ownership-map)
Your own site
<a href="https://agentmods.dev/skills/tercumantanumut/selene/security-ownership-map"><img src="https://agentmods.dev/badge/skills/tercumantanumut/selene/security-ownership-map/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 security-ownership-map

Your own site · 80×15
<a href="https://agentmods.dev/skills/tercumantanumut/selene/security-ownership-map"><img src="https://agentmods.dev/badge/skills/tercumantanumut/selene/security-ownership-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,109 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 88% copy Near-identical to another mod 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.00099 $0.02109
Opus 5 $0.00049 $0.01055
Sonnet 5 $0.00020 $0.00422
Haiku 4.5 $0.00010 $0.00211

Measured 11d ago against content hash eb3851405453, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

security-ownership-map 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 11d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/build_ownership_map.py, scripts/community_maintainers.py, scripts/query_ownership.py, …), 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.

Origin

This is a copy

88% identical to security-ownership-map — 52 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

lib/skills/catalog/bundled/security-ownership-map/SKILL.md · 207 lines

How it starts

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

Security Ownership Map

Overview

Build a bipartite graph of people and files from git history, then compute ownership risk and export graph artifacts for Neo4j/Gephi. Also build a file co-change graph (Jaccard similarity on shared commits) to cluster files by how they move together while ignoring large, noisy commits.

Requirements

  • Python 3
  • networkx (required; community detection is enabled by default)

Install with:

pip install networkx

Workflow

  1. Scope the repo and time window (optional --since/--until).
  2. Decide sensitivity rules (use defaults or provide a CSV config).
  3. Build the ownership map with ${SELENE_SKILL_ROOT}/scripts/run_ownership_map.py (co-change graph is on by default; use --cochange-max-files to ignore supernode commits).
  4. Communities are computed by default; graphml output is optional (--graphml).
  5. Query the outputs with ${SELENE_SKILL_ROOT}/scripts/query_ownership.py for bounded JSON slices.
  6. Persist and visualize (see ${SELENE_SKILL_ROOT}/references/neo4j-import.md).

By default, the co-change graph ignores common “glue” files (lockfiles, .github/*, editor config) so clusters reflect actual code movement instead of shared infra edits. Override with --cochange-exclude or --no-default-cochange-excludes. Dependabot commits are excluded by default; override with --no-default-author-excludes or add patterns via --author-exclude-regex.

If you want to exclude Linux build glue like Kbuild from co-change clustering, pass:

python "${SELENE_SKILL_ROOT}/scripts/run_ownership_map.py \
  --repo /path/to/linux \
  --out ownership-map-out \
  --cochange-exclude "**/Kbuild"

Quick start

Run from the repo root:

python "${SELENE_SKILL_ROOT}/scripts/run_ownership_map.py \
  --repo . \
  --out ownership-map-out \
  --since "12 months ago" \
  --emit-commits

Defaults: author identity, author date, and merge commits excluded. Use --identity committer, --date-field committer, or --include-merges if needed.

Read the full file on GitHub · 207 lines

Files

What ships with it

5 files 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.

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. 11d ago First seen · 207 lines · 99 tokens per session scan A eb3851405453

Subscribe to this mod's changes

security-ownership-map is a skill published in the GitHub repository tercumantanumut/selene (168 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 2,109 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to security-ownership-map, differing in 52 lines, and is treated as a copy.

Related

Other skills, from other repositories

conventional-git

Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent…

samber/cc-skills · 111 tokens

security-ownership-map

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Use when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example…

tech-leads-club/agent-skills · 107 tokens

gh-address-comments

Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…

tech-leads-club/agent-skills · 85 tokens

review

Review current uncommitted git changes with full file context and produce a structured report with severity levels, actionable fixes, and an approval verdict.

buiducnhat/cobrew · 30 tokens

superpowers-using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.

KornLabs/truss · 39 tokens

composio-changelog-generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

KornLabs/truss · 51 tokens