メニュー
Look up every package this repository publishes across all registries via packages.ecosyste.ms, with downloads, dependent counts, latest version, and registry URL.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | packages |
| description | Look up every package this repository publishes across all registries via packages.ecosyste.ms, with downloads, dependent counts, latest version, and registry URL. |
| license | MIT |
| compatibility | Needs network access to packages.ecosyste.ms. |
| metadata | {"scrutineer.version":1,"scrutineer.output_file":"report.json","scrutineer.output_kind":"packages","scrutineer.requires_remote":true} |
One repository can ship multiple packages across multiple ecosystems. Ask packages.ecosyste.ms for all of them and record the headline stats.
./context.json — has repository.url./report.json — write the packages array here./schema.json — output shape./context.json and extract repository.url.https://packages.ecosyste.ms/api/v1/packages/lookup?repository_url={URL-ENCODED_URL}. The response is a JSON array, one object per published package.report.json under packages mapping these fields:
name from upstream nameecosystem from upstream ecosystem (e.g. rubygems, npm, pypi)purl from upstream purllicenses from upstream licenses (string, comma-joined if upstream gives a list)latest_version from upstream latest_release_number or latest_versionversions_count from upstream versions_countdownloads from upstream downloadsdependent_packages from upstream dependent_packages_countdependent_repos from upstream dependent_repos_countregistry_url from upstream registry_url or the registry's canonical package pagelatest_release_at from upstream latest_release_published_at (RFC3339)dependent_packages_url from upstream dependent_packages_urlmetadata — the whole upstream object for this package, verbatimIf there are no packages (lookup returns []), write {"packages": []}. That is a valid result, not an error.