Security ownership map
Maps who owns sensitive code from Git history and highlights bus-factor risk and code nobody looks after.
When to use it
- You want to know who maintains authentication or payment code.
- Sensitive areas may depend on one person.
- You are writing or checking a CODEOWNERS file.
It only runs when you ask about security ownership.
A practical example
You ask
“Who owns our auth and billing code, and where are we exposed?”
Your agent does
It analyses commit history for sensitive paths and reports owners, gaps and single points of failure.
What gets installed
The whole folder is copied, so scripts, references and any license notices stay together.
- agents/openai.yaml253 bytes
- LICENSE.txt10,776 bytes
- references/neo4j-import.md2,428 bytes
- scripts/build_ownership_map.py34,330 bytes
- scripts/community_maintainers.py18,122 bytes
- scripts/query_ownership.py17,991 bytes
- scripts/run_ownership_map.py5,890 bytes
- SKILL.md9,019 bytes
Credit and license
An original workflow that incorporates OpenAI’s security review material. It’s shared under the Apache License 2.0, and the license file is installed with it however you choose to install.