Audits entire codebase for security risks including secrets exposure and misconfigurations.
npx skills add https://github.com/mia-cx/.agents --skill audit-security-mia-cx
Please help me install this Agent Skill. Skill: audit-security Source: https://github.com/mia-cx/.agents/tree/main/skills/audit-security Command: npx skills add https://github.com/mia-cx/.agents --skill audit-security-mia-cx
Run a whole-codebase security audit — secrets scanning, trust boundary analysis, OWASP Top 10 evaluation, configuration review, and dependency audit. Use when a user wants a security review of the entire project (not just a PR), and when the repository is described with terms like "security audit", "pen test", "hardening", or "vulnerability scan".
Override the Security Reviewer’s scope to cover the entire repository and run a full codebase security assessment.
High-intent search queries and answers about installing and using this skill.
A whole-codebase security audit scans for secrets exposure, trust boundary issues, configuration weaknesses, and vulnerable dependencies. It evaluates the OWASP Top 10 across the entire repository rather than just reviewing PR diffs.
Automated secrets scanning checks all tracked files in the repository to surface credentials and sensitive data. It identifies exposed secrets across the entire codebase during a comprehensive security audit.
The security audit includes a comprehensive configuration and access review that checks CORS, authentication, CSP, and dev-mode exposure. It identifies configuration weaknesses across the repository to prevent unauthorized access.
Dependency audit coordination with the Security Reviewer surfaces known vulnerable components and provides remediation recommendations. This dependency audit is part of the comprehensive codebase security assessment.
Use a full-repo vulnerability scan when you need comprehensive hardening, pentest, or threat modeling across the entire project. PR-only reviews miss cross-component risks, whereas full-repo analysis maps trust boundaries and identifies data flow weaknesses.
Trust boundary mapping is a full-repo threat modeling technique that identifies cross-component risks and data flow weaknesses. It analyzes the entire codebase to surface security risks where data crosses trust boundaries.
ahravPackage git-tracked source files into a tar.gz archive, excluding binaries and build artifacts.
micaelmaltaIdentify and remediate security vulnerabilities across code, configuration, and architecture.
nikhillinitDetect security vulnerabilities, secrets, and misconfigurations in codebases.
igbuendGenerates a security-focused DISCOVERY.md for code review and threat modeling.
