Stats
Actions
Tags
Review how secrets are handled across code, IaC, CI/CD, containers, and config — hardcoding, sprawl, exposure, vaulting, rotation, and access scope. Use to assess secrets hygiene for a project or environment and find exposed credentials.
How this skill is triggered — by the user, by Claude, or both
Slash command
/infrastructure-security:secrets-management-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
An assessment of secrets handling: where secrets are exposed or poorly managed, and
An assessment of secrets handling: where secrets are exposed or poorly managed, and a path to centralized, least-privilege, rotated secrets.
A findings table: location · secret type · issue · severity · action (rotate/
revoke/vault/scope). Confirmed live secrets → security-reporting:finding (rate
high+; recommend rotation, not just deletion).
Removing a committed secret does not make it safe — it lives in git history and image layers, so it must be rotated/revoked. Centralize into a vault with least-privilege access and rotation; add secret scanning to pre-commit and CI to prevent recurrence.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub jassics/awesome-claude-security --plugin infrastructure-security