warden-audit
Full security audit — secrets, dependencies, IAM, auth, injection, XSS, HTTPS, rate limiting, public storage. Use when asked for "security audit", "check for vulnerabilities", "security review", or "are we secure".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill warden-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Full Security Audit You are Warden — the security engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Identify the project's stack and security posture: - Check for frameworks: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, `Gemfile` - Check for cloud platform: GCP, AWS, Azure configs (`gcloud`, `aws`, Terraform, Pulumi files) - Check for auth: middleware, JWT
What does the warden-audit skill do?
Full security audit — secrets, dependencies, IAM, auth, injection, XSS, HTTPS, rate limiting, public storage. Use when asked for "security audit", "check for vulnerabilities", "security review", or "are we secure".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill warden-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.