owasp/secure-agent-playbook

prompt-injection-test

Test LLM-integrated applications against known prompt injection techniques, evasion methods, and attack intents using the Arcanum PI Taxonomy.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/owasp/secure-agent-playbook --skill prompt-injection-test

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Prompt Injection Testing

Systematically test an LLM application's prompt injection defenses by following the full procedure in plays/prompt-injection-testing.md.

Based on the Arcanum PI Taxonomy by Jason Haddix (Arcanum Information Security). CC BY 4.0.

Steps

  1. Scope and Input Surface Mapping — Identify all paths where attacker-controlled content reaches the LLM: direct (chat, API params) and indirect (file uploads, web fetches, RAG docs, tool outputs, MCP resources).
  1. Test by Attack Intent (13 intents) — For each authorized intent, attempt to achieve the attacker's goal:
  • INT-01 System Prompt Leak, INT-02 Jailbreak, INT-03 Tool Enumeration
  • INT-04 API Enumeration, INT-05 Get Prompt Secret, INT-06 Attack Users
  • INT-07 Data Poisoning, INT-08 Denial of Service, INT-09 Discuss Harm
  • INT-10 Multi-Chain Attacks, INT-11 Generate Image, INT-12 Test Bias
  • INT-13 Business Integrity
  1. Test by Attack Technique (18 techniques) — Apply known payload construction methods:
  • Framing, Narrative Smuggling, Cognitive Overload, Meta-Prompting
  • Russian Doll, Memory Exploitation, Act as Interpreter, Contradiction
  • End Sequences, Inversion, Rule Addition, Variable Expansion
  • Link Injection, Puzzling, Anti-Harm Coercion, ASCII/Spatial
  • Binary Streams, Spatial Byte Arrays
  1. Apply Evasion Layers (20 evasions) — When techniques are blocked, retry with obfuscation:
  • Encoding: base64, hex, morse, cipher, reverse
  • Language: alt language, fictional language, phonetic substitution, emoji
  • Structural: JSON/XML wrapping, markdown, metacharacter confusion, whitespace, splats
  • Advanced: steganography, link smuggling, graph nodes, waveforms, case changing
  1. Execute Test Matrix — Combine intents x techniques x evasions. Prioritize: high-impact intents first, indirect surfaces second, evasion sweeps against defenses that blocked direct attempts.
  1. Assess Results — For each successful injection, document: severity, attack path (intent + technique + evasion + surface), exact payload, detection gap, and remediation.
  1. Defense Validation — Check the 5-layer defense checklist: ecosystem hardening, model guardrails, prompt-layer defenses, data-layer controls, application-layer validation.

Output

Test results summary table (intent / technique / evasion / surface / result / severity), detailed findings using templates/finding.md, defense coverage checklist with gaps highlighted, and prioritized recommendations.

OWASP References

  • LLM01: Prompt Injection
  • LLM05: Improper Output Handling
  • LLM06: Excessive Agency
  • LLM07: System Prompt Leakage

Related by task

from this repository

More skills

All skills
owasp
Community

web-security-review

Review web applications against the OWASP Top 10 for Web Applications (2021). Use when auditing web apps, reviewing server-side code, or assessing web frameworks for the classic OWASP Top 10 risks including injection, broken auth, and XSS.

1h installs
2
GitHub stars
209
Updated
Oct 15
owasp
Community

api-security-review

Comprehensive API security review against OWASP API Security Top 10 (2023). Use when reviewing OpenAPI/Swagger specs, auditing REST/GraphQL/gRPC implementations, testing authentication mechanisms, or checking API gateway configurations. Covers BOLA/IDOR, broken auth, mass assignment, rate limiting, SSRF, and more with real-world attack scenarios.

1h installs
1
GitHub stars
204
Updated
Oct 15
owasp
Community

code-review-security

Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.

1h installs
1
GitHub stars
184
Updated
Sep 25
owasp
Community

llm-risk-assess

Comprehensive LLM security assessment against OWASP Top 10 for LLM Applications 2025. Use when reviewing LLM-integrated applications, RAG pipelines, chatbots, AI agents, or GenAI features. Covers prompt injection, data poisoning, supply chain, excessive agency, and more with real-world attack scenarios and testing methodologies.

1h installs
1
GitHub stars
184
Updated
Sep 25