security-auditor

Automate interactive security audits of codebases using the Map & Probe methodology.

4|3|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Artifex1/auditor-addon --skill security-auditor-artifex1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/Artifex1/auditor-addon/tree/main/skills/security-auditor
Command: npx skills add https://github.com/Artifex1/auditor-addon --skill security-auditor-artifex1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Conducts interactive security audits of codebases using the Map & Probe methodology to identify vulnerabilities early and guide remediation.

Core Features & Use Cases

  • Structural mapping of codebases (MAP) to inventory components and identify potential risk areas.
  • Optional CHECKLIST generation for identified standards and per-path PROBE deep analysis.
  • Per-path PROBE with actionable findings and traceable evidence to support remediation.

Quick Start

Invoke the security-auditor skill to start a Map phase and proceed to Probe.

Frequently Asked Questions about security-auditor

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

FAQPage Schema
How do I conduct a structured security audit of my codebase?▼

A structured security audit automates codebase inventory, standards checks, and per-path vulnerability analysis using the Map & Probe methodology to identify risk areas and guide remediation with traceable evidence.

What is the Map and Probe methodology for vulnerability detection?▼

The Map and Probe methodology first inventories codebase components to identify structural risk areas, then performs deep per-path analysis on specific paths to generate actionable vulnerability findings.

Can I use automated code review to check for risk patterns in large projects?▼

Automated code review applies to codebases of varying sizes where structured inventory and risk pattern assessment are needed, using code scanning and path enumeration to evaluate vulnerabilities.

How do I generate a checklist for security standards during a code audit?▼

You can generate a checklist for identified standards after the structural mapping phase, which then informs the optional per-path deep analysis to probe specific code paths for vulnerabilities.

Does this security audit approach require specific plugins to scan code?▼

The security audit requires Read, Glob, Grep, and custom mcp auditor plugins to perform code scanning, path enumeration, and risk assessment across the target codebase.