Injection Testing

Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.

49 stars 7 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mn-youssef/security-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mn-youssef/security-skills --skill injection-testing
Manual install
git clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/injection-testing ~/.claude/skills/injection-testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Injection Testing (FIND/EXPLOIT — input reaches an interpreter)

## Overview
Injection happens when input crosses into a language an interpreter executes — SQL, a shell, a
template engine, an XML/LDAP/XPath parser. This skill *proves* it dynamically; the code-level
patterns live in `security-code-audit/references/database.md` and `api-backend.md`.

**Core principle:** Find where input changes the *structure* of a command, not just its data.
A working injection is a tiny structural payload that changes the interpreter's behavior.

## Applies when / Skip when
- **Applies when:** untrusted input can reach an interpreter — SQL/NoSQL DB, OS shell, template
  engine, or XML/LDAP/XPath parser.
- **Skip when:** a given sink type is absent → that injection class is N/A.
- **If N/A:** name the absent interpreters (e.g. "no SQL → SQLi N/A") and test only the sinks
  that exist. Partial applicability is normal here.

## ⚠️ Authorization
Your own/authorized app, non-prod for stateful payloads. Never `--dump` real data, never
`--os-shell`/RCE on shared systems, never `; DROP`/destructive payloads. Confirm, don't damage.

## Method
1. **Map sinks** — every input that could reach a query/command/template/parser (use the audit findings).
2. **Probe** — send a structure-breaking character and watch for a behavior change (error,
   different result, timing).
3. **Confirm** — escalate from "something changed" to a controlled, benign proof.
Read the full skill on GitHub

Details

Skill name
injection-testing
Path
skills/injection-testing/SKILL.md
License
MIT
Repo updated
12 June 2026

FAQ

What does the Injection Testing skill do?

Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.

How do I install the Injection Testing skill?

Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Injection Testing popular?

It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.

Related skills

Access Control Testing

49

mn-youssef/security-skills

Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.

Testing & QA

Active Pentest

49

mn-youssef/security-skills

Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.

Security

API Security Testing

49

mn-youssef/security-skills

Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.

Security

Spec Driven Test

32

Loveforwa/spec-test.skill

Use specification-based testing methodology for end-to-end testing of web applications. Use this skill when users request "test this feature", "check this feature completeness", "do E2E testing on this project", "test this web app with an agent", or directly mention spec-driven-test / specification-based testing. This skill also applies to scenarios where users want to automatically generate test specs and test cases from code, then execute tests through browser automation. Even if users don't explicitly mention "spec" or "test case", if they want to systematically and automatically test a spe

Testing & QA

File Upload and Ssrf

49

mn-youssef/security-skills

Use when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. On apps you own or are authorized to test.

Testing & QA

Spec Driven Test

32

Loveforwa/spec-test.skill

用规约驱动测试(specification-based testing)的方法对 web 应用做端到端测试。当用户说要"测试一下这个功能"、"检查一下这个功能的完整性"、"对这个项目做 E2E 测试"、"用 agent 测这个 web 应用"或者直接提到 spec-driven-test / specification-based testing 时使用这个 skill。也适用于用户希望基于代码自动生成测试规约和测试用例,然后通过浏览器自动化执行测试的场景。即使用户没有明确说"规约"或"测试用例"这些词,只要他想系统地、自动化地测试一个 web 项目的某个功能,都应该使用这个 skill。

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.