95 tagged supply-chain-security, measured the same way as everything else here.
Browse within: agent-security 76static-analysis 73formal-verification 72sbom 21devsecops 20cli 16appsec 14appsec-tools 14branch-protection 14secure-by-default 14go 13openssf-scorecard 13purl 13github-actions 7
Skill Claude Code
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Skill Claude Code
Deep-dive security risk analysis for a dependency flagged by uzomuzo diet.
Skill Claude CodeCodex
Use before installing, updating, auditing, or executing dependencies, package-manager commands, project generators, CI actions/workflows, release jobs, IDE extensions, MCP servers, or AI-agent tools. Also use when investigating suspected compromise or advisories, debugging publish or release authentication, or…
CaseyLabs/kc-secure-repo-template
Skill Claude CodeCodex
Review or update GitHub repository hardening guidance and its Terraform implementation under config/infra, including rulesets, required checks, scanning, permissions, provider pins, and plan/apply safety. Do not use for ordinary app code, generic template adaptation, release integrity, or routine workflow validation.
Skill Claude CodeCodex
Generates a changelog entry from recent commits.
Skill Claude CodeCodex
Lineage-aware skill evaluation — before installing or recommending any third-party agent skill, trace its family tree (forks, same-name rewrites, credited derivatives), drop pure mirrors, find the family member that actually fits, and screen derivative additions for stowaway instructions. Value for the user — install…
Skill Claude CodeCodex
A tool for finding, comparing, checking, and installing existing agent skills from different sources. It groups copies of the same skill and checks them for suspicious content before installation.
Skill Claude CodeCodex
Use when a local Agent runtime process must be inspected or verified against an explicit runtime expectation, especially after an install or upgrade.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: