Security Ownership Map

Analyze git-history security ownership when sensitive files, CODEOWNERS coverage, bus factor, contributor concentration, and remediation evidence need mapping.

9 stars 4 forksSecurity

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill security-ownership-map
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/security-ops/security-ownership-map ~/.claude/skills/security-ownership-map

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Security Ownership Map

## Philosophy
- Map ownership risk for sensitive paths from repository evidence.
- Start from live evidence and local patterns.
- Apply the context-disposition policy: move important still-valid context to references, and intentionally discard stale, duplicated, unsafe, superseded, or low-signal text.

## When To Use
- The user asks who owns sensitive files or where bus factor is low.
- CODEOWNERS needs comparison against observed contributors.
- Audit, onboarding, ownership transfer, or remediation planning needs evidence.

## Avoid
- Personal accountability claims beyond observable repo evidence.
- Raw secret, private email, or sensitive commit content in chat.
- Destructive git commands or target repo mutation.

## Inputs
- repo path
- time window
- sensitive-path rules
- CODEOWNERS policy
- author/committer model

## Outputs
- ownership-risk summary
- bus-factor findings
- sensitive-path evidence
- artifact paths
- remediation
- Schema-bound outputs include schema_version.

## Workflow
- Start with 2-3 focused surfaces before expanding scope.
- Confirm scope, time window, and attribution model.
- Run or adapt the archived ownership-map scripts when needed.
- Compare observed maintainers with CODEOWNERS and sensitivity rules.
- Redact sensitive details and summarize only evidence-backed risk.
- Recommend backup owners, review policy, or knowledge transfer.

## Constraints
- Treat git history as partial evidence.
Read the full skill on GitHub

Details

Skill name
security-ownership-map
Path
Skills/security-ops/security-ownership-map/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Security Ownership Map skill do?

Analyze git-history security ownership when sensitive files, CODEOWNERS coverage, bus factor, contributor concentration, and remediation evidence need mapping.

How do I install the Security Ownership Map skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill security-ownership-map. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Security Ownership Map popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

1password

9

jscraik/Agent-Skills

Plan, diagnose, and validate 1Password CLI workflows. Use when tasks need op CLI sign-in, secret references, op run, op inject, item reads, env injection, or service-account secret access.

Security

Agentation

9

jscraik/Agent-Skills

Audit, validate, and troubleshoot Agentation integrations in frontend apps. Use when annotations, MCP registration, endpoint sync, webhook delivery, or watch mode readiness are failing.

AI, LLMs & Agents

Agents Md

9

jscraik/Agent-Skills

Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance for stale or conflicting rules against current model documentation, scoped routing, deduplication, or progressive disclosure.

AI, LLMs & Agents

Talk Katsioloudes Code Security AI

9

jscraik/Agent-Skills

Answers questions about, summarises key insights from, and applies the security guidance of Joseph Katsioloudes's talk 'Code Security Reinvented: Navigating the era of AI'. Use when the user asks about AI-assisted secure coding, MCP servers, skills, agentic workflows, the 1-to-100 security-to-developer gap, start left vs shift left, task flows, LLM-as-judge, supply-chain decisions, AI-assisted fuzzing, hallucinations and non-determinism in AI security review, GitHub Security Lab resources, or applying the talk's security framework to AI-assisted development.

Security

Recon Workbench

9

jscraik/Agent-Skills

Run, audit, and design authorized Recon Workbench workflows when scoped target interrogation needs evidence artifacts, redaction, validation, and safe reporting.

Security

Talk Tal Skills Security

9

jscraik/Agent-Skills

Defensive review of AI-agent skills, plugins, and tools using Liran Tal's security principles. Use when assessing provenance, permissions, data exposure, sandboxing, or approval boundaries before adoption.

Security

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.