@khalidsaidi/skillrunner 0.1.2 → 0.1.3

package/dist/registry/skills/openai-security-ownership-map/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: openai-security-ownership-map
+description: "Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions. (Imported from openai upstream skills)"
+version: "1.0.0"
+tags: ["openai", "upstream", "imported"]
+kind: knowledge
+risk: low
+availability: advanced
+docs:
+  source: "https://github.com/openai/skills/tree/main/skills/.curated/security-ownership-map"
+---
+
+# openai-security-ownership-map
+
+Imported upstream skill.
+
+- Provider source: https://github.com/openai/skills/tree/main/skills/.curated/security-ownership-map
+- Original skill name: security-ownership-map
+
+## Upstream Content
+
+# Security Ownership Map
+
+## Overview
+
+Build a bipartite graph of people and files from git history, then compute ownership risk and export graph artifacts for Neo4j/Gephi. Also build a file co-change graph (Jaccard similarity on shared commits) to cluster files by how they move together while ignoring large, noisy commits.
+
+## Requirements
+
+- Python 3
+- `networkx` (required; community detection is enabled by default)
+
+Install with:
+
+```bash
+pip install networkx
+```
+
+## Workflow
+
+1. Scope the repo and time window (optional `--since/--until`).
+2. Decide sensitivity rules (use defaults or provide a CSV config).
+3. Build the ownership map with `scripts/run_ownership_map.py` (co-change graph is on by default; use `--cochange-max-files` to ignore supernode commits).
+4. Communities are computed by default; graphml output is optional (`--graphml`).
+5. Query the outputs with `scripts/query_ownership.py` for bounded JSON slices.
+6. Persist and visualize (see `references/neo4j-import.md`).
+
+By default, the co-change graph ignores common “glue” files (lockfiles, `.github/*`, editor config) so clusters reflect actual code movement instead of shared infra edits. Override with `--cochange-exclude` or `--no-default-cochange-excludes`. Dependabot commits are excluded by default; override with `--no-default-author-excludes` or add patterns via `--author-exclude-regex`.
+
+If you want to exclude Linux build glue like `Kbuild` from co-change clustering, pass:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo /path/to/linux \
+  --out ownership-map-out \
+  --cochange-exclude "**/Kbuild"
+```
+
+## Quick start
+
+Run from the repo root:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --since "12 months ago" \
+  --emit-commits
+```
+
+Defaults: author identity, author date, and merge commits excluded. Use `--identity committer`, `--date-field committer`, or `--include-merges` if needed.
+
+Example (override co-change excludes):
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --cochange-exclude "**/Cargo.lock" \
+  --cochange-exclude "**/.github/**" \
+  --no-default-cochange-excludes
+```
+
+Communities are computed by default. To disable:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --no-communities
+```
+
+## Sensitivity rules
+
+By default, the script flags common auth/crypto/secret paths. Override by providing a CSV file:
+
+```
+# pattern,tag,weight
+**/auth/**,auth,1.0
+**/crypto/**,crypto,1.0
+**/*.pem,secrets,1.0
+```
+
+Use it with `--sensitive-config path/to/sensitive.csv`.
+
+## Output artifacts
+
+`ownership-map-out/` contains:
+
+- `people.csv` (nodes: people)
+- `files.csv` (nodes: files)
+- `edges.csv` (edges: touches)
+- `cochange_edges.csv` (file-to-file co-change edges with Jaccard weight; omitted with `--no-cochange`)
+- `summary.json` (security ownership findings)
+- `commits.jsonl` (optional, if `--emit-commits`)
+- `communities.json` (computed by default from co-change edges when available; includes `maintainers` per community; disable with `--no-communities`)
+- `cochange.graph.json` (NetworkX node-link JSON with `community_id` + `community_maintainers`; falls back to `ownership.graph.json` if no co-change edges)
+- `ownership.graphml` / `cochange.graphml` (optional, if `--graphml`)
+
+`people.csv` includes timezone detection based on author commit offsets: `primary_tz_offset`, `primary_tz_minutes`, and `timezone_offsets`.
+
+## LLM query helper
+
+Use `scripts/query_ownership.py` to return small, JSON-bounded slices without loading the full graph into context.
+
+Examples:
+
+```bash
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out people --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag auth --bus-factor-max 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out person --person alice@corp --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out file --file crypto/tls
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out cochange --file crypto/tls --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section orphaned_sensitive_code
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out community --id 3
+```
+
+Use `--community-top-owners 5` (default) to control how many maintainers are stored per community.
+
+## Basic security queries
+
+Run these to answer common security ownership questions with bounded output:
+
+```bash
+# Orphaned sensitive code (stale + low bus factor)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section orphaned_sensitive_code
+
+# Hidden owners for sensitive tags
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section hidden_owners
+
+# Sensitive hotspots with low bus factor
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section bus_factor_hotspots
+
+# Auth/crypto files with bus factor <= 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag auth --bus-factor-max 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag crypto --bus-factor-max 1
+
+# Who is touching sensitive code the most
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out people --sort sensitive_touches --limit 10
+
+# Co-change neighbors (cluster hints for ownership drift)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out cochange --file path/to/file --min-jaccard 0.05 --limit 20
+
+# Community maintainers (for a cluster)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out community --id 3
+
+# Monthly maintainers for the community containing a file
+python skills/skills/security-ownership-map/scripts/community_maintainers.py \
+  --data-dir ownership-map-out \
+  --file network/card.c \
+  --since 2025-01-01 \
+  --top 5
+
+# Quarterly buckets instead of monthly
+python skills/skills/security-ownership-map/scripts/community_maintainers.py \
+  --data-dir ownership-map-out \
+  --file network/card.c \
+  --since 2025-01-01 \
+  --bucket quarter \
+  --top 5
+```
+
+Notes:
+- Touches default to one authored commit (not per-file). Use `--touch-mode file` to count per-file touches.
+- Use `--window-days 90` or `--weight recency --half-life-days 180` to smooth churn.
+- Filter bots with `--ignore-author-regex '(bot|dependabot)'`.
+- Use `--min-share 0.1` to show stable maintainers only.
+- Use `--bucket quarter` for calendar quarter groupings.
+- Use `--identity committer` or `--date-field committer` to switch from author attribution.
+- Use `--include-merges` to include merge commits (excluded by default).
+
+### Summary format (default)
+
+Use this structure, add fields if needed:
+
+```json
+{
+  "orphaned_sensitive_code": [
+    {
+      "path": "crypto/tls/handshake.rs",
+      "last_security_touch": "2023-03-12T18:10:04+00:00",
+      "bus_factor": 1
+    }
+  ],
+  "hidden_owners": [
+    {
+      "person": "alice@corp",
+      "controls": "63% of auth code"
+    }
+  ]
+}
+```
+
+## Graph persistence
+
+Use `references/neo4j-import.md` when you need to load the CSVs into Neo4j. It includes constraints, import Cypher, and visualization tips.
+
+## Notes
+
+- `bus_factor_hotspots` in `summary.json` lists sensitive files with low bus factor; `orphaned_sensitive_code` is the stale subset.
+- If `git log` is too large, narrow with `--since` or `--until`.
+- Compare `summary.json` against CODEOWNERS to highlight ownership drift.

package/dist/registry/skills/openai-security-ownership-map/upstream/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/dist/registry/skills/openai-security-ownership-map/upstream/SKILL.md

@@ -0,0 +1,206 @@
+---
+name: "security-ownership-map"
+description: "Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions."
+---
+
+# Security Ownership Map
+
+## Overview
+
+Build a bipartite graph of people and files from git history, then compute ownership risk and export graph artifacts for Neo4j/Gephi. Also build a file co-change graph (Jaccard similarity on shared commits) to cluster files by how they move together while ignoring large, noisy commits.
+
+## Requirements
+
+- Python 3
+- `networkx` (required; community detection is enabled by default)
+
+Install with:
+
+```bash
+pip install networkx
+```
+
+## Workflow
+
+1. Scope the repo and time window (optional `--since/--until`).
+2. Decide sensitivity rules (use defaults or provide a CSV config).
+3. Build the ownership map with `scripts/run_ownership_map.py` (co-change graph is on by default; use `--cochange-max-files` to ignore supernode commits).
+4. Communities are computed by default; graphml output is optional (`--graphml`).
+5. Query the outputs with `scripts/query_ownership.py` for bounded JSON slices.
+6. Persist and visualize (see `references/neo4j-import.md`).
+
+By default, the co-change graph ignores common “glue” files (lockfiles, `.github/*`, editor config) so clusters reflect actual code movement instead of shared infra edits. Override with `--cochange-exclude` or `--no-default-cochange-excludes`. Dependabot commits are excluded by default; override with `--no-default-author-excludes` or add patterns via `--author-exclude-regex`.
+
+If you want to exclude Linux build glue like `Kbuild` from co-change clustering, pass:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo /path/to/linux \
+  --out ownership-map-out \
+  --cochange-exclude "**/Kbuild"
+```
+
+## Quick start
+
+Run from the repo root:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --since "12 months ago" \
+  --emit-commits
+```
+
+Defaults: author identity, author date, and merge commits excluded. Use `--identity committer`, `--date-field committer`, or `--include-merges` if needed.
+
+Example (override co-change excludes):
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --cochange-exclude "**/Cargo.lock" \
+  --cochange-exclude "**/.github/**" \
+  --no-default-cochange-excludes
+```
+
+Communities are computed by default. To disable:
+
+```bash
+python skills/skills/security-ownership-map/scripts/run_ownership_map.py \
+  --repo . \
+  --out ownership-map-out \
+  --no-communities
+```
+
+## Sensitivity rules
+
+By default, the script flags common auth/crypto/secret paths. Override by providing a CSV file:
+
+```
+# pattern,tag,weight
+**/auth/**,auth,1.0
+**/crypto/**,crypto,1.0
+**/*.pem,secrets,1.0
+```
+
+Use it with `--sensitive-config path/to/sensitive.csv`.
+
+## Output artifacts
+
+`ownership-map-out/` contains:
+
+- `people.csv` (nodes: people)
+- `files.csv` (nodes: files)
+- `edges.csv` (edges: touches)
+- `cochange_edges.csv` (file-to-file co-change edges with Jaccard weight; omitted with `--no-cochange`)
+- `summary.json` (security ownership findings)
+- `commits.jsonl` (optional, if `--emit-commits`)
+- `communities.json` (computed by default from co-change edges when available; includes `maintainers` per community; disable with `--no-communities`)
+- `cochange.graph.json` (NetworkX node-link JSON with `community_id` + `community_maintainers`; falls back to `ownership.graph.json` if no co-change edges)
+- `ownership.graphml` / `cochange.graphml` (optional, if `--graphml`)
+
+`people.csv` includes timezone detection based on author commit offsets: `primary_tz_offset`, `primary_tz_minutes`, and `timezone_offsets`.
+
+## LLM query helper
+
+Use `scripts/query_ownership.py` to return small, JSON-bounded slices without loading the full graph into context.
+
+Examples:
+
+```bash
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out people --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag auth --bus-factor-max 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out person --person alice@corp --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out file --file crypto/tls
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out cochange --file crypto/tls --limit 10
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section orphaned_sensitive_code
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out community --id 3
+```
+
+Use `--community-top-owners 5` (default) to control how many maintainers are stored per community.
+
+## Basic security queries
+
+Run these to answer common security ownership questions with bounded output:
+
+```bash
+# Orphaned sensitive code (stale + low bus factor)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section orphaned_sensitive_code
+
+# Hidden owners for sensitive tags
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section hidden_owners
+
+# Sensitive hotspots with low bus factor
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out summary --section bus_factor_hotspots
+
+# Auth/crypto files with bus factor <= 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag auth --bus-factor-max 1
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out files --tag crypto --bus-factor-max 1
+
+# Who is touching sensitive code the most
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out people --sort sensitive_touches --limit 10
+
+# Co-change neighbors (cluster hints for ownership drift)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out cochange --file path/to/file --min-jaccard 0.05 --limit 20
+
+# Community maintainers (for a cluster)
+python skills/skills/security-ownership-map/scripts/query_ownership.py --data-dir ownership-map-out community --id 3
+
+# Monthly maintainers for the community containing a file
+python skills/skills/security-ownership-map/scripts/community_maintainers.py \
+  --data-dir ownership-map-out \
+  --file network/card.c \
+  --since 2025-01-01 \
+  --top 5
+
+# Quarterly buckets instead of monthly
+python skills/skills/security-ownership-map/scripts/community_maintainers.py \
+  --data-dir ownership-map-out \
+  --file network/card.c \
+  --since 2025-01-01 \
+  --bucket quarter \
+  --top 5
+```
+
+Notes:
+- Touches default to one authored commit (not per-file). Use `--touch-mode file` to count per-file touches.
+- Use `--window-days 90` or `--weight recency --half-life-days 180` to smooth churn.
+- Filter bots with `--ignore-author-regex '(bot|dependabot)'`.
+- Use `--min-share 0.1` to show stable maintainers only.
+- Use `--bucket quarter` for calendar quarter groupings.
+- Use `--identity committer` or `--date-field committer` to switch from author attribution.
+- Use `--include-merges` to include merge commits (excluded by default).
+
+### Summary format (default)
+
+Use this structure, add fields if needed:
+
+```json
+{
+  "orphaned_sensitive_code": [
+    {
+      "path": "crypto/tls/handshake.rs",
+      "last_security_touch": "2023-03-12T18:10:04+00:00",
+      "bus_factor": 1
+    }
+  ],
+  "hidden_owners": [
+    {
+      "person": "alice@corp",
+      "controls": "63% of auth code"
+    }
+  ]
+}
+```
+
+## Graph persistence
+
+Use `references/neo4j-import.md` when you need to load the CSVs into Neo4j. It includes constraints, import Cypher, and visualization tips.
+
+## Notes
+
+- `bus_factor_hotspots` in `summary.json` lists sensitive files with low bus factor; `orphaned_sensitive_code` is the stale subset.
+- If `git log` is too large, narrow with `--since` or `--until`.
+- Compare `summary.json` against CODEOWNERS to highlight ownership drift.

package/dist/registry/skills/openai-security-ownership-map/upstream/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Security Ownership Map"
+  short_description: "Map maintainers, bus factor, and sensitive code ownership"
+  default_prompt: "Build a security ownership map for this repository and identify bus-factor risks in sensitive code."