security-audit

Audit codebases for vulnerabilities, insecure configurations, and dependency CVEs.

Updated May 8, 2026
One-click install
npx skills add https://github.com/freire19/Mythos --skill security-audit-freire19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/freire19/Mythos/tree/main/skills/security-audit
Command: npx skills add https://github.com/freire19/Mythos --skill security-audit-freire19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security-audit helps you identify vulnerabilities, vulnerable dependencies, and risky configuration patterns in a codebase before they become real incidents.

Core Features & Use Cases

  • Automated vulnerability scanning: Runs SAST, dependency CVE checks, and misconfiguration audits across the project.
  • Targeted manual review: Reviews high-risk areas such as auth logic, input validation, injection surfaces, file handling, crypto usage, session/token handling, and error disclosure.
  • Actionable reporting: Produces a destructive-style report with file/line context, attack vector, concrete code fixes, severity, and CWE mapping, plus explicit exclusions and a sprint-based action plan.

Quick Start

Ask Mythos to run a full security audit on my repository and include a line-referenced report with attack vectors, severity, CWE mapping, and a prioritized fix plan.

Frequently Asked Questions about security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full security audit on my code repository to find vulnerabilities?

Run a full security audit by performing sequential recon, automated SAST scanning, dependency CVE checks, and hotspot review to locate vulnerabilities and insecure configurations, ending with a structured report of severity and CWE mappings.

What does SAST scanning and dependency CVE analysis cover in a codebase review?

SAST scanning and dependency CVE analysis cover full-spectrum security auditing to locate vulnerabilities, insecure configurations, and risky dependency patterns across the target codebase before real incidents occur.

Can I map CWE identifiers and severity levels to discovered attack vectors?

Yes, you can map CWE identifiers and severity levels to attack vectors. The security audit produces a structured report including file and line context, attack vectors, severity levels, and explicit CWE mapping.

What high-risk areas does a manual security review target for authentication and crypto logic?

A manual security review targets high-risk areas such as authentication logic, input validation, injection surfaces, file handling, crypto usage, session and token handling, and error and logging practices for vulnerabilities.

Does the vulnerability report include concrete code fixes and a prioritized action plan?

Yes, the vulnerability report includes concrete code fixes. It produces a destructive-style report with file and line context, attack vectors, severity, CWE mapping, and a sprint-based prioritized fix plan.