agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/security-ownership-map/SKILL.md

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

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.
  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

  • GoogleSkill

    improve-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

  • OpenAISkill

    test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    Also in 3 projects that use this

  • MicrosoftSkill

    grill-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 CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

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
  1. Distinctive:

    Every security-relevant component has a named owner, escalation path, and stated decision rights, or is explicitly flagged unowned.

    line 22

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Enumerate security-relevant components: authentication, authorization, secrets handling, data stores holding sensitive data, external integrations, deployment and CI, and the network edge.
  2. 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.
  3. 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).
  4. 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.
  5. Flag shared-ownership components where responsibility is genuinely ambiguous; these are where findings stall longest.
  6. 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.
  7. Note cross-boundary components — vendor-managed, contractor-built, or inherited — and record the contractual or practical limit on what can be changed.
  8. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.