security-ownership-map
Skill220 starsChanged 19 days agoMITView on GitHub
Use when security findings or incident responsibilities are stalling because component ownership and decision rights are unclear—derive an evidence-backed map from code ownership, commit, deploy, and on-call records; record patch, shutdown, and credential-rotation authority; and flag unowned, departed, shared, vendor, or powerless owners. This routes remediation; it is not a system threat model.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- tkbk-online/skillstheir own version, first seen Nov 15, 2026
- jgeofil/agent-skillstheir own version, first seen Nov 8, 2026
- hmjBill/skillstheir own version, first seen Oct 29, 2026
- kushvinth/skillstheir own version, first seen Oct 29, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- PracticalSwan/agent-skillstheir own version, first seen Oct 19, 2026
Used with
Projects with it also use interview-me, improve-codebase-architecture and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 4 projects that use this
OpenAISkilltest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Also in 3 projects that use this
MicrosoftSkillgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Also in 3 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- openai/skills★ 27ksame name
- z91772524-ai/pojia-next-mac★ 39same name
- sampleXbro/agentsmesh★ 27same name
- PracticalSwan/agent-skills★ 22same name
- jscraik/Agent-Skills★ 9same name
- AymanShams/codex-coding-os★ 1same name
- FuSheng-MG/Pi-Agent-skills★ 1same name
- davidanthonyn/claude-skills★ 0same name
- hebertzhu/agent-foundry★ 0same name
- hmjBill/skills★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository179 other files it gives its agents.
- AGENTS.mdAGENTS.md
- chrono/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- accessible-media-authoringSkill
- agentic-safety-auditSkill
- agent-prompt-engineeringSkill
- audio-event-map-authoringSkill
- auto-scaffoldSkill
- chain-constructSkill
- chain-construct-smart-contractSkill
- claim-verificationSkill
- code-reachability-auditSkill
- code-review-loopSkill
- color-theorySkill
- conversation-designSkill
- copy-refinementSkill
- cosmos-sdk-audit-checklistSkill
- cross-chain-bridge-auditSkill
- cross-file-relationship-synthesisSkill
- data-flow-traceSkill
- dedup-prior-art-checkSkill
- defi-invariant-checkSkill
- dependency-cycle-auditSkill
- dependency-health-triageSkill
- detection-as-codeSkill
- diff-aware-semgrep-scanSkill
- differential-reviewSkill
- dimensional-analysis-checkSkill
- dual-level-retrievalSkill
- durable-nonce-exploitationSkill
- erc1271-revert-data-checkSkill
- error-based-sstiSkill
- evm-audit-flowSkill
- figma-implement-designSkill
- findings-filterSkill
- forensic-timeline-authoringSkill
- game-design-fundamentalsSkill
- game-mechanics-balancingSkill
- head-tailSkill
- incident-response-runbookSkill
- interactive-audio-designSkill
- interface-ambiguity-checkSkill
- keyword-clusteringSkill
- knowledge-base-integrationSkill
- known-advisory-backport-checkSkill
- layered-analysis-loopSkill
- level-design-patternsSkill
- locale-adaptationSkill
- multi-stance-audit-fanoutSkill
- narrative-structureSkill
- osint-platform-auditSkill
- parser-differential-route-confusionSkill
- persuasive-technical-writingSkill
- platform-complianceSkill
- player-engagement-psychologySkill
- pre-audit-threat-modelSkill
- program-rubric-lookupSkill
- read-only-reentrancy-checkSkill
- requirements-elicitationSkill
- review-severity-ladderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Every security-relevant component has a named owner, escalation path, and stated decision rights, or is explicitly flagged unowned.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Ownership Map
Establish who owns each security-relevant component, so findings route to someone who can act and no surface is left unowned.
Steps
- Enumerate security-relevant components: authentication, authorization, secrets handling, data stores holding sensitive data, external integrations, deployment and CI, and the network edge.
- For each component, derive candidate owners from evidence — code ownership files, commit history concentration, deploy configuration, and on-call rotations — rather than from an org chart.
- Record for each component: owning team or person, escalation path, and the decision rights they actually hold (can they patch, can they take it offline, can they rotate its credentials).
- Flag every component with no owner, a departed owner, or an owner who lacks the rights to remediate. Unowned security surface is itself a finding.
- Flag shared-ownership components where responsibility is genuinely ambiguous; these are where findings stall longest.
- Map each finding class to the owner who can remediate it, distinguishing the owner of the code from the owner of the deployment where these differ.
- Note cross-boundary components — vendor-managed, contractor-built, or inherited — and record the contractual or practical limit on what can be changed.
- Date the map and name its evidence sources; ownership decays and an undated map silently misroutes.
Acceptance
- Every security-relevant component has a named owner, escalation path, and stated decision rights, or is explicitly flagged unowned.
- Ownership is derived from observable evidence, with the source cited per component.
- Components whose owner cannot remediate are called out separately from unowned ones.
- Finding classes are routed to the owner able to act on them.
- The map carries a date and its evidence sources.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

