audit-3-review

Validate and correct audit-2-scan vulnerability findings in post-scan review workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted effort and incorrect remediation by validating each reported vulnerability from a previous code audit, removing false positives, and correcting severity or fix quality.

Core Features & Use Cases

  • Issue contra-verification: Rechecks every issue produced by audit-2-scan (01-07) to confirm it is a real bug or an intentional behavior, verify the proposed fix does not introduce new issues, and ensure the severity level is correct.
  • Gap discovery: Looks for additional problems audit-2-scan may have missed, including cross-module interactions, deployment/infra configuration risks, and transitive dependency issues.
  • Actionable review report: Saves a structured output to docs/audits/temp/08_review.md covering discarded false positives, severity adjustments, corrected fixes, newly found problems, and declared blind spots.

Quick Start

Ask the agent to run audit-3-review after audit-2-scan has produced files 01-07 in docs/audits/temp/.

Frequently Asked Questions about audit-3-review

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

FAQPage Schema
How do I validate static analysis findings and remove false positives from a code audit?

Static analysis false positives are validated by contra-verifying each reported vulnerability to confirm it is a real bug, checking the proposed fix for new issues, and adjusting severity levels in a structured markdown review report.

What is the best way to find missed vulnerabilities and cross-module interactions after a code scan?

Finding missed vulnerabilities requires performing targeted gap discovery for cross-module interactions, deployment configuration risks, and transitive dependency issues beyond the initial scan output to ensure comprehensive security coverage.

Can I correct severity levels and fix quality for vulnerabilities found during a security audit?

Severity levels and fix quality can be corrected by rechecking every issue from the prior scan, verifying the proposed remediation does not introduce new issues, and adjusting the severity level to match the actual risk.

What scan artifacts are required to start a post-scan vulnerability review workflow?

A post-scan vulnerability review requires detecting expected scan artifacts numbered 01-07 plus a 00_setup.md file located in the docs/audits/temp/ directory to validate findings and generate a deterministic report.

How do I generate a structured code auditing report covering discarded false positives and newly found problems?

A structured code auditing report is generated by saving a markdown file covering discarded false positives, severity adjustments, corrected fixes, newly found problems, and declared blind spots to the docs/audits/temp/ directory.