audit-2-scan

Audit code defects and vulnerabilities across seven categories with CVE reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find real, fixable defects and security weaknesses in your codebase before deployment by performing a structured, destructive review across critical engineering categories.

Core Features & Use Cases

  • End-to-end destructive scan: Reviews bugs/runtime risks, security issues (including dependency vulnerabilities via the package manager audit), business logic, resilience/error handling, performance, maintainability, and tests.
  • Category-by-category reporting: Writes results into separate files under docs/audits/temp/ for traceable, incremental remediation.
  • Actionable issue formatting: Produces numbered issues with severity, file/line location, impact, problematic code, and a suggested fix.
  • Security package audit integration: Requires running the appropriate package manager audit (e.g., npm audit) and reporting CRITICAL/HIGH vulnerabilities as individual issues with CVE and fixed versions.

Quick Start

Ask the agent to run the audit scan on your project after you have completed audit-1-setup, specifying whether you want the full 7-category scan or only the security category.

Frequently Asked Questions about audit-2-scan

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

FAQPage Schema
How do I run a comprehensive code audit to find security vulnerabilities and bugs?

A comprehensive code audit scans your project across seven categories including security, runtime risks, and business logic to identify fixable defects. It reviews dependency vulnerabilities using package manager audits and outputs categorized reports with severity and suggested fixes.

What is a destructive code review and how does it differ from standard testing?

A destructive code review proactively searches for defects, security weaknesses, and runtime risks across your codebase rather than validating expected behavior. It evaluates maintainability, error handling, and test quality to uncover vulnerabilities before deployment.

How do I check my project for CRITICAL npm dependency vulnerabilities with CVE fixes?

Running a package manager security audit like npm audit identifies CRITICAL and HIGH vulnerabilities in your dependencies. The scan reports individual issues with CVE identifiers and fixed versions so you can resolve them systematically.

Can I scan only the security category instead of running a full project audit?

Yes, you can narrow the audit scan to specific categories such as security only. This focuses the review exclusively on security issues and package vulnerabilities, bypassing the other six categories like performance or maintainability.

Do I need to prepare my project environment before running a code audit scan?

Yes, you must complete the initial audit setup phase first. The scan verifies the existence of the setup file in your audits directory before executing the sequential seven-category review and writing categorized output reports.

What format does the code audit report use for tracking and fixing issues?

The audit generates categorized markdown files under a dedicated audits directory. Each file contains numbered issues detailing severity, file and line location, impact, problematic code snippets, and suggested fixes for incremental remediation.