security-audit

Review code changes for prompt injection, path traversal, and command injection vulnerabilities.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents introduce attack surfaces beyond traditional application security, such as malicious memory files, unsafe tool calls, and credential leakage. This Skill provides a structured checklist to audit code changes against these agent-specific threats before they ship. ## Core Features & Use Cases - Agent-Specific Threat Coverage: Detects prompt injection via MEMORY.md/USER.md, path traversal through tool calls, command injection via shell tools, and data exfiltration through fetch_url. - Audit Checklist: Verifies whether changes bypass trust/permission systems, skip memory safety scans, expose API keys in logs, or fetch external URLs without sandbox policy checks. - Aixlarity Source Mapping: Points reviewers to key security boundaries including trust.rs, agent/permissions.rs, tools/memory_tool.rs, and tools/container.rs. - Use Case: Before merging a pull request that adds a new tool to an AI agent, run this audit to confirm the tool respects the three-level trust model and does not create a new path for untrusted input to reach shell commands. ## Quick Start Use the security-audit skill to review my latest code changes for prompt injection, path traversal, and permission bypass vulnerabilities.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I audit AI agent code for security vulnerabilities?

Check every code change against agent-specific threats: prompt injection through memory files, path traversal in tool calls, command injection via shell tools, and exfiltration through fetch_url. Verify the change does not bypass the trust or permission system.

What is prompt injection in AI coding agents?

Prompt injection occurs when malicious content written to files like MEMORY.md or USER.md alters agent behavior. Defenses include pattern scanning in memory tooling, such as the checks implemented in memory_tool.rs.

How do I prevent path traversal in agent tool calls?

Path traversal happens when an agent requests files outside allowed boundaries, such as read_file with ../../etc/passwd. A trust system that restricts file access scopes is the primary defense against this attack vector.

What security boundaries should an AI agent harness have?

Key boundaries include a multi-level trust model, permission prompt logic for tool calls, memory safety scanning, and container sandboxing. In Aixlarity these map to trust.rs, agent/permissions.rs, tools/memory_tool.rs, and tools/container.rs.

When should a security audit block a code change?

Block changes that create new paths for user input to reach shell commands, bypass permission checks, write to memory files without safety scans, expose API keys in output or logs, or fetch external URLs without sandbox policy enforcement.