Agent skill · Security

ai-security

Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill ai-security --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 17 KB
Bundled scripts: yes
Path: engineering-team/skills/ai-security/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AI Security AI and LLM security assessment skill for detecting prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, and agent tool abuse. This is NOT general application security (see security-pen-testing) or behavioral anomaly detection in infrastructure (see threat-detection) — this is about security assessment of AI/ML systems and LLM-based agents specifically. --- ## Table of Contents - [Overview](#overview) - [AI Threat Scanner Tool](#ai-threat-scanner-tool) - [Prompt Injection Detection](#prompt-injection-detection) - [Jailbreak Assessment](#jailbreak-assessment) - [Model Inversion Risk](#model-inversion-risk) - [Data Poisoning Risk](#data-poisoning-risk) - [Agent Tool Abuse](#agent-tool-abuse) - [MITRE ATLAS Coverage](#mitre-atlas-coverage) - [Guardrail Design Patterns](#guardrail-design-patterns) - [Workflows](#workflows) - [Anti-Patterns](#anti-patterns) - [Cross-References](#cross-references) --- ## Overview ### What This Skill Does This skill provides the methodology and tooling for **AI/ML security assessment** — scanning for prompt injection signatures, scoring model inversion and data poisoning risk, mapping findings to MITRE A

What's inside
Steps it walks through
  1. Table of Contents
  2. Overview
  3. What This Skill Does
  4. Distinction from Other Security Skills
  5. Prerequisites
  6. AI Threat Scanner Tool
  7. Test File Format
  8. Exit Codes
  9. Prompt Injection Detection
  10. Injection Signature Categories
  11. Injection Score
  12. Indirect Injection via External Content
  13. Jailbreak Assessment
  14. Jailbreak Taxonomy
Ships with 2 files
  • references/atlas-coverage.md
  • scripts/ai_threat_scanner.py
Commands it runs
Scan built-in seed prompts for a black-box LLM
python3 scripts/ai_threat_scanner.py \
Scan a custom test file with gray-box access (requires --authorized)
Assess a classifier for adversarial robustness
Scope to specific threat categories
List all injection signature names with ATLAS IDs
python3 scripts/ai_threat_scanner.py --list-patterns
Full assessment across all target types
for target in llm classifier embedding; do
echo "=== ${target} ==="
More from claude-skills
All skills →
About this skill
What does the ai-security skill do?

Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill ai-security --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going