Menu
Index the repository's dependencies via `git-pkgs list`, recording manifest path, ecosystem, and requirement per entry.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | dependencies |
| description | Index the repository's dependencies via `git-pkgs list`, recording manifest path, ecosystem, and requirement per entry. |
| license | MIT |
| compatibility | Requires `git-pkgs` (https://github.com/git-pkgs/git-pkgs) and `python3` on PATH. |
| metadata | {"scrutineer.version":1,"scrutineer.output_file":"report.json","scrutineer.output_kind":"dependencies","scrutineer.paths":["**"],"scrutineer.ignore_paths":["**/node_modules/**","**/dist/**","**/generated/**","**/__generated__/**","**/*.min.js","**/*.min.css"]} |
Wrap git-pkgs list --format json so scrutineer can read the result as a dependencies report. Preserve dependency phase/type fields from git-pkgs; scrutineer normalizes common aliases to runtime, dev, test, or build. Scrutineer's worker resolves Maven requirements from local pom.xml files with git-pkgs/pom, fills requirement_resolution, and marks unresolved placeholders with requirement_unresolved.
./src — the cloned repository./scripts/index.sh — the wrapper script./report.json — write the final report here./schema.json — output shapescripts/index.sh — runs git-pkgs init then git-pkgs list --format json inside ./src, normalises empty or null output to an empty array, and writes {"dependencies": [...]}.Run the script and capture its stdout as the report:
bash scripts/index.sh > ./report.json
If the script exits non-zero, read its stderr, then write a short {"dependencies": [], "error": "..."} document to ./report.json so the caller sees why no dependencies were indexed.
The wrapper already emits the exact schema the parser expects — no post-processing needed. Do not merge test, build, development, and runtime dependencies together; keep the phase/type field on each row when git-pkgs reports one.
Do not inspect manifests yourself, infer dependencies from files that git-pkgs did not report, or hand-author dependency rows. If the wrapper returns {"dependencies":[]}, write that exact report and stop. Missing coverage in git-pkgs should produce an empty dependency report, not model-authored package data.
Map distinct externally reachable input-processing subsystems into focus areas for the threat-model skill to carry into later security audits. This is a short, read-only orientation pass, not a vulnerability scan.
Derive a project's security contract from its source and docs, then emit it as structured data other skills can cite. Records what the project assumes about callers and inputs, what properties it claims and disclaims, which code is out of scope, and which recurring tool findings are known-safe. This is not a vulnerability scan; it produces the trust map that security-deep-dive loads instead of re-deriving boundaries per run.
Default pipeline scrutineer runs when a repository is added. Triggers a standard set of other skills in parallel, then writes a short summary of what was enqueued. Edit the list below to change the default scan coverage without touching scrutineer's Go code.
Audit first-party source for security vulnerabilities using an inventory-first, six-step per-sink methodology. Use when you want a thorough scan that distinguishes real findings from pattern matches and records both in a machine-readable report. The target is this codebase's own code, not its dependencies.
Compare open findings in one repository and record how they relate. Marks same-vulnerability findings as duplicates, findings that another finding's fix will close as subsumed, and findings that combine into a higher-severity attack as a chain.
High-recall static source-code vulnerability scan adapted from Anthropic's defending-code reference harness. Fans out by focus area, ranks candidates by confidence, and emits Scrutineer findings for later verification.