agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/security-ownership-map/SKILL.md

security-ownership-map

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks for security-oriented ownership analysis, bus-factor analysis, sensitive-code ownership, orphaned sensitive code, CODEOWNERS reality checks for risk, hidden maintainers, security maintainer mapping, sensitive hotspots, ownership clusters, co-change ownership risk, or people-to-file topology grounded in git history. Use to analyze git repositories and export CSV, JSON, GraphML, or graph artifacts for security ownership visualization. Do not use for general maintainer lists, generic team ownership, normal git blame, non-security ownership questions, broad code review, threat modeling, secure coding best practices, or dependency impact analysis. If the primary task is AppSec threat modeling, use security-threat-model. If the primary task is language/framework security guidance or a vulnerability report, use security-best-practices. If the primary task is graph-backed code dependency impact, use code-review-graph.

  • Installs packages

14 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview-me, test-driven-development and 1 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

  • OpenAISkill

    test-driven-development

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

    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

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 3 are common, 0 are distinctive, and 11 are very specific to this project.

  • 3

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 13 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.

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.

Check your setup, free