ai-threat-testing

ai-threat-testing is a skill for Claude Code from transilienceai/communitytools. It costs 55 tokens per session (1,140 once invoked), scanned A, original, MIT.

A security-testing framework for applications that use large language models, such as chatbots or AI APIs. It checks for risks including prompt injection, data leaks, model theft, poisoned data, and unsafe dependencies.

In plain words
What is it for?
It helps test an AI application or model endpoint against the OWASP Top 10 for Large Language Model Applications, either as a full assessment or for selected weaknesses.
Why use it?
It helps reveal AI-specific attacks that ordinary application testing may miss. It also records evidence and produces proof-of-concept examples for authorized assessments.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Part of the communitytools plugin — 48 skills, 5 commands, 9 agents, 1 hook shipped together

Good fit It helps test an AI application or model endpoint against the OWASP Top 10 for Large Language Model Applications, either as a full assessment or for selected weaknesses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/transilienceai/communitytools/ai-threat-testing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add transilienceai/communitytools --skill ai-threat-testing
Clone the repo
git clone --depth 1 https://github.com/transilienceai/communitytools

Made for: Claude Code.

Or install communitytools, the plugin that ships this one along with the rest of its 48 skills, 5 commands, 9 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ai-threat-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/transilienceai/communitytools/ai-threat-testing/github.svg)](https://agentmods.dev/skills/transilienceai/communitytools/ai-threat-testing)
Your own site
<a href="https://agentmods.dev/skills/transilienceai/communitytools/ai-threat-testing"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/ai-threat-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ai-threat-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/transilienceai/communitytools/ai-threat-testing"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/ai-threat-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01140
Opus 5 $0.00028 $0.00570
Sonnet 5 $0.00011 $0.00228
Haiku 4.5 $0.00006 $0.00114

Measured 10d ago against content hash 1cb1b256b1c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ai-threat-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ai-threat-testing/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Threat Testing

Test LLM applications for OWASP LLM Top 10 vulnerabilities using 10 specialized agents. Use for authorized AI security assessments.

Quick Start

1. Specify target (LLM app URL, API endpoint, or local model)
2. Select scope: Full OWASP Top 10 | Specific vulnerability | Supply chain
3. Agents deploy, test, capture evidence
4. Professional report with PoCs generated

Coverage — OWASP LLM Top 10, 2025 edition

Which file addresses which category is decided by reference/catalog/llm-top10-2025.json, not by the filename. The llmNN- prefixes on disk predate the 2025 renumbering and no longer match; the content is correct, the labels were not. Cite an id only with its edition (LLM06:2025), because a bare LLM06 means two different categories depending on which edition the reader assumes.

Category Attack surface
LLM01:2025 Prompt Injection Direct and indirect injection, instruction override, filter evasion
LLM02:2025 Sensitive Information Disclosure Training-data and cross-tenant RAG leakage, canary verification
LLM03:2025 Supply Chain Dependency CVEs, model provenance, malicious serialized models
LLM04:2025 Data and Model Poisoning Backdoor triggers, membership inference, behavioural anomalies
LLM05:2025 Improper Output Handling Code/XSS injection downstream, unsafe deserialization
LLM06:2025 Excessive Agency Tool/plugin abuse, privilege escalation, unauthorised actions — the category that matters for agents rather than chatbots
LLM07:2025 System Prompt Leakage Gap — no playbook yet. See the catalogue: what the prompt contains is a separate finding from whether it can be extracted
LLM08:2025 Vector and Embedding Weaknesses RAG injection, retrieval manipulation, embedding inversion
LLM09:2025 Misinformation Hallucination and confidence manipulation where output is relied upon
LLM10:2025 Unbounded Consumption Token flooding, cost impact, and model extraction/theft (2025 treats extraction-by-query as a consumption problem)

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 108 lines · 55 tokens per session scan A 1cb1b256b1c5

Subscribe to this mod's changes

ai-threat-testing is a skill published in the GitHub repository transilienceai/communitytools (520 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,140 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.