ai-audit-mcp

Audit code contexts to identify and report exploitability findings.

80|6|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/yunmengya/PHP_AUDIT_SKILLS --skill ai-audit-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-audit-mcp
Source: https://github.com/yunmengya/PHP_AUDIT_SKILLS/tree/main/ai-audit-mcp
Command: npx skills add https://github.com/yunmengya/PHP_AUDIT_SKILLS --skill ai-audit-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of conducting in-depth security audits using AI, transforming raw code context into actionable exploitability findings.

Core Features & Use Cases

  • AI-First Auditing: Leverages AI models to analyze code context for security vulnerabilities.
  • Contextual Analysis: Processes detailed code context including routes, call graphs, function bodies, and file contents.
  • Exploitability Reporting: Outputs normalized findings with details on source, sink, taint, and proof-of-concept.
  • Use Case: After an initial static analysis generates a code context, this Skill uses an AI to deeply audit that context, identifying and detailing potential vulnerabilities like SQL injection or RCE.

Quick Start

Run the ai-audit-mcp skill to audit the provided AI audit context for project 'my-php-app'.

Frequently Asked Questions about ai-audit-mcp

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

FAQPage Schema
How does AI-driven vulnerability analysis identify exploitability in PHP code?

AI-driven vulnerability analysis identifies exploitability by processing detailed code context, including routes, call graphs, and function bodies, to generate normalized reports on sources, sinks, and taint for PHP vulnerabilities like SQL injection or RCE.

What code context is needed to perform an AI security audit?

To perform an AI security audit, you need specific context JSON files that contain detailed code context, including routes, call graphs, function bodies, and file contents, which the AI analyzes to identify potential security vulnerabilities.

Do I need a local Claude CLI to run AI security audits on generated code?

Yes, you need a local Claude CLI to run AI security audits, as the Skill leverages Claude models to deeply analyze the provided code context and generate normalized vulnerability reports with proof-of-concept details.

How do I audit code context for security vulnerabilities using AI?

You audit code context by running the Skill against your prepared context JSON files; the AI analyzes the provided routes, call graphs, and file contents to output normalized findings detailing source, sink, taint, and proof-of-concept exploitability.

What is the best way to report SQL injection or RCE vulnerabilities found via code review?

The best way to report SQL injection or RCE vulnerabilities is by generating normalized findings that detail the source, sink, taint, and proof-of-concept, which AI auditing automatically produces from the analyzed code context.

Can I use this AI audit approach without a pre-existing static analysis context?

No, this AI audit approach requires a pre-existing static analysis context; it functions by deeply auditing specific context JSON files generated from a prior analysis to identify and detail potential code vulnerabilities.