Skip to content
Back to skills

Ai Llm Security Review

ASecurity

Use for AI/LLM security assessments, prompt injection, RAG security, agent/tool permissioning, model supply chain, LLM red teaming, AI governance, eval design, data leakage, jailbreak testing, and secure AI application review.

  • 65 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 12, 2026
ai-agentsrustgotestingsecurity

Security analysis

A100/100

Scanned June 12, 2026

npx -y skills add 26zl/cybersec-toolkit --skill ai-llm-security-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ai Llm Security Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ai Llm Security Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/26zl-ai-llm-security-review/badge)](https://www.skillsdirectory.com/skills/26zl-ai-llm-security-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ai-llm-security-review
description: Use for AI/LLM security assessments, prompt injection, RAG security, agent/tool permissioning, model supply chain, LLM red teaming, AI governance, eval design, data leakage, jailbreak testing, and secure AI application review.
---

# AI and LLM security review

Use this skill for AI applications, agents, RAG systems, model gateways, prompt chains, evals, and LLM governance.

## Review workflow

1. Inventory the AI system: model/provider, prompts, tools, RAG sources, memory, logs, user roles, secrets, data classes, and downstream actions.
2. Threat model trust boundaries:
   - user input to prompt
   - retrieved content to model
   - model output to tools
   - tool output to user
   - logs/traces to operators
3. Test high-risk paths:
   - direct and indirect prompt injection
   - data exfiltration from RAG or memory
   - insecure tool invocation
   - overbroad agent permissions
   - jailbreaks that change policy or role
   - model/provider key leakage
   - training/eval data contamination
4. Recommend controls:
   - least-privilege tool scopes
   - allowlisted tool schemas and argument validation
   - retrieval filtering and source attribution
   - secret redaction before prompts/logs
   - output validation before side effects
   - human approval for destructive or external actions
   - continuous evals and regression prompts

## Deliverables

Return findings as:

| Risk | Attack path | Impact | Evidence | Control | Test to keep fixed |
| --- | --- | --- | --- | --- | --- |

When the task involves current AI regulation or sector obligations, verify against current official sources before making definitive claims.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…