Skip to main content
command CX Codex

security-audit · florianbruniaux — Claude Code command: security audit

The security-audit command for Claude Code and Codex inspects a project alongside Claude Code settings. It checks for exposed secrets, dependency flaws, injection risks, and hook issues, then returns a score and remediation plan.

CC-BY-SA-4.0 ★ 6,529 updated 2026-11-14

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/security-audit.md
Open on GitHub

What security-audit does

The command reviews a project and its Claude Code configuration across six areas, then creates a scored report out of 100 with fixes ranked by priority. It searches for exposed credentials and prompt-injection signals, audits dependencies, and checks security hooks and settings. The configuration review runs /security-check.

Dependency checks use npm audit, pip-audit, cargo audit, or govulncheck, depending on the project files. If no package manager is detected, that phase is skipped without a score penalty. The report gives results for each phase and assigns a grade from A to F.

What it helps with

  • find credentials committed in project files
  • inspect Markdown and config files for injection signals
  • audit dependencies with the matching package tool
  • review Claude Code security hooks and settings

Example prompts for the agent

  • Run a full security audit of this project and its Claude Code settings.
  • Check dependencies, exposed credentials, and hooks, then rank the fixes.
  • Assess prompt-injection risks and give the project a security score.

How to install security-audit

Manually: put the files in place

.claude/commands/security-audit.md

Call it with /security-audit. For all projects use ~/.claude/commands/

Questions about security-audit

How do I install security-audit in Claude Code?

Save the command as .claude/commands/security-audit.md.

What does security-audit do?

It checks credentials, Claude Code configuration, prompt-injection risks, dependencies, and security hooks. The final report includes a security grade and prioritized remediation plan.

Which tools does security-audit use for dependency checks?

It runs npm audit, pip-audit, cargo audit, or govulncheck according to the project files. If no package manager is detected, it skips that phase.

Similar slash commands

All slash commands for Security →

security-audit by other authors comes first.

security-audit davila7 security-audit runs a structured security review on your codebase, dependencies, and configuration. Handy before shipping to production or during code audits. CX Codex +1 1,485installs security-audit centminmod The security-audit command scans a codebase for vulnerabilities and unsafe patterns across a project or a specific module. CX Codex +1 ★ 2,744repo stars mcp-security-audit official github mcp-security-audit scans .mcp.json files for hardcoded secrets, shell injection patterns, and unpinned package dependencies. Runs before commits or when onboarding new MCP servers to a repository. CX Codex +1 1,100installs security boshu2 This skill reviews code, dependencies, secrets, and prompt surfaces for security risks. Use it for a pre-release review or a repository scan. CX Codex +1 1,400installs security-reviewer sangrokjung security-reviewer scans a diff for OWASP Top 10 flaws, hardcoded secrets and shaky dependencies, then ranks what it finds. You get a report with secure code samples. CX Codex ★ 880repo stars dependency-audit davila7 dependency-audit audits project dependencies for known CVEs, license compliance issues, and outdated packages across multiple ecosystems. CX Codex +1 658installs vibe-security Chris Raroque vibe-security — a skill that audits apps built fast with an AI assistant: leaked keys, broken database access rules, and trust placed in values coming from the client. CX Codex +1 3,900installs security-auditor zhaono1 security-auditor — a skill that hunts vulnerabilities in your code: walks the OWASP Top 10, checks configs, dependencies and leaked secrets. Useful before a release or a review. CX Codex +1 1,100installs

From the same set45

The whole set →
methodology-advisor The methodology-advisor command for Claude Code and Codex reads the codebase and asks three questions to recommend an AI-development methodology stack. Run it at the start of a project, before choosing a workflow. CX Codex +1 ★ 6,529repo stars source-command-methodology-advisor source-command-methodology-advisor inspects your repository, asks three focused questions, and suggests an engineering methodology stack for coding with AI. CX Codex +1 ★ 6,529repo stars boldguy-linkedin-answer boldguy-linkedin-answer is a Claude Code command that drafts a LinkedIn comment tied to relevant parts of a Claude Code guide. It reads a post from its URL and writes in the post’s language. CX Codex +1 ★ 6,529repo stars release Carries a guide release through the whole chain: semver bump, drafted changelog, count checks across docs, landing sync, commit and push. CX Codex +1 ★ 6,529repo stars update-infos-release The update-infos-release command for Claude Code tracks upstream releases and syncs guide, landing page, and MCP server data; version increments are optional. CX Codex +1 ★ 6,529repo stars self-assessment The self-assessment skill for Claude Code tests your knowledge across ten Claude topics, identifies your level and gaps, then builds a learning path that respects prerequisites. CX Codex +1 ★ 6,529repo stars source-command-track-mentions source-command-track-mentions scans the web for third-party citations of the Claude Code guide or author projects and syncs confirmed links into tracking files. CX Codex +1 ★ 6,529repo stars audit-repo-docs The audit-repo-docs command checks repository documentation against 30 criteria and produces a scored report with prioritized fixes. It spots gaps in README files, docs structure, and automation. CX Codex +1 ★ 6,529repo stars

Project sponsors

Companies that keep this analytics open