security-ai

Reviews LLM applications, AI agents, MCP servers, and AI supply chains for security vulnerabilities.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/akoita/agent-toolkit --skill security-ai-akoita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ai
Source: https://github.com/akoita/agent-toolkit/tree/main/plugins/claude/security/skills/security-ai
Command: npx skills add https://github.com/akoita/agent-toolkit --skill security-ai-akoita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? AI systems place language models in trust-bearing positions where they read attacker-controlled text, choose tool calls, and gate access to data, and conventional security review checklists do not cover the resulting risks like prompt injection, exfiltration through rendering layers, and agent permission bypass. This Skill provides structured, evidence-driven review checklists for every surface where a model sits in the trust path. ## Core Features & Use Cases - Surface-based review routing: Identifies which of six surfaces a target has — LLM application, agent runtime, MCP server, AI/ML supply chain, skill-shipping repository, or model-assisted vulnerability analysis — and applies the matching checklist from dedicated reference files. - Structural control verification: Enforces the rule that a control existing only in a prompt is not a control, checking harness-enforced permissions, sandboxing, egress proxies, credential isolation, and rail-enforced spend limits instead. - Restricted vulnerability analysis profile: Ships a fail-closed JSON profile template and a standard-library Python validator that must pass before any model-assisted source analysis begins. - Use Case: When reviewing an agent that reads GitHub issues and runs shell commands, use this Skill to map its indirect-injection paths, verify its sandbox and egress controls, and produce findings with severity, confidence, evidence, and remediation per the shared reporting contract. ## Quick Start Ask the agent to perform a security review of your LLM application or MCP server using the security-ai skill and report findings with severity and evidence.

Frequently Asked Questions about security-ai

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

FAQPage Schema
How do I security review an LLM application for prompt injection?▼

Start with the lethal trifecta check: identify components that simultaneously access private data, read untrusted content, and communicate externally. Then enumerate every indirect injection path through tool results and retrieved documents, and audit the rendering layer for exfiltration channels like Markdown images and link prefetching.

How do I review an MCP server for security vulnerabilities?▼

Review in two passes: first verify normative OAuth 2.1 requirements like token audience validation, resource indicators, and the prohibition on tokens in URIs. Then check ecosystem risks the specification does not cover, including tool poisoning, rug-pulls, cross-server tool shadowing, and mutable launch commands.

What tools can I use for AI red teaming in CI?▼

promptfoo is the recommended choice for CI gating because it has a documented failure exit code and an official GitHub Action. garak probes model endpoints but lacks a pass/fail exit code, while PyRIT and DeepTeam offer multi-turn attack orchestration with gating you build yourself.

Does safetensors make a model file safe to load?▼

No. safetensors guarantees no code execution only for the tensor file itself, not for the config.json, modeling code, tokenizer files, or chat templates shipped alongside it. Those files must be read and grepped for eval, exec, subprocess, and network calls.

When should I not use this AI security review skill?▼

Skip it when no model or agent sits in the trust path and a conventional application, infrastructure, or dependency review applies instead. It is also not appropriate for producing legal or regulatory compliance sign-off.

How do I run model-assisted vulnerability analysis safely on private source code?▼

Complete the restricted-analysis-profile JSON template, which fixes read-only source paths, an external private artifact directory, credential and network restrictions, and tool denials. Validate it with the bundled Python validator script before exposing any source to the analysis process.