PluginBench
Skill
Fail
Audit score 45

injection-checking

yaklang/hack-skills

Route injection vulnerabilities to the correct testing skill based on interpreter type.

What is injection-checking?

Entry point for identifying and categorizing injection-class vulnerabilities. Use this when attacker-controlled input reaches a dangerous interpreter (HTML, SQL, templates, shell, etc.) to determine whether to pursue XSS, SQLi, SSRF, XXE, SSTI, command injection, NoSQL injection, or other injection variants.

  • Routes injection issues to specialized skills (XSS, SQLi, SSRF, XXE, SSTI, CMDi, NoSQL, etc.)
  • Identifies the final sink where input is consumed
  • Maps input flow to the correct interpreter context
  • Provides quick triage without redundant payload routing
  • Links to 18+ injection-type skills for deep-dive testing

How to install injection-checking

npx skills add https://github.com/yaklang/hack-skills --skill injection-checking
Claude Code
Cursor
Windsurf
Cline

How to use injection-checking

  1. 1.Identify where attacker-controlled input is consumed (HTML, SQL, shell, template engine, XML parser, etc.)
  2. 2.Determine the interpreter or execution environment
  3. 3.Select the corresponding skill from the skill map (XSS, SQLi, SSRF, XXE, SSTI, CMDi, NoSQL, etc.)
  4. 4.Follow the chosen skill's workflow for payload testing and exploitation

Use cases

Good for
  • Determine if user input in a web form leads to XSS or SQLi based on how it's processed
  • Identify whether a URL parameter triggers SSRF or SSTI by tracing execution context
  • Route XML parsing vulnerabilities to XXE or XSLT injection skills
  • Classify command execution issues as CMDi vs. deserialization attacks
  • Triage NoSQL injection vs. SQL injection in database queries
Who it's for
  • Security testers routing between injection vulnerability types
  • Penetration testers deciding which injection skill to apply first
  • Code reviewers identifying dangerous input sinks
  • Developers learning injection vulnerability taxonomy

injection-checking FAQ

When should I use this skill vs. going directly to XSS or SQLi?

Use this skill when you haven't yet determined the injection type. It helps you identify the correct sink and interpreter context before diving into a specific injection variant.

Does this skill include payload samples?

No. Payload samples and quick triage are merged into each specialized skill (XSS, SQLi, etc.). This skill routes you to the right one.

What if input reaches multiple interpreters?

Identify the primary or most dangerous sink first, then test that injection type. Secondary sinks can be tested afterward using their respective skills.

Are all injection types covered by the skill map?

The skill map covers 18+ injection variants including XSS, SQLi, SSRF, XXE, SSTI, CMDi, NoSQL, deserialization, JNDI, expression language, CRLF, SSI, LDAP, XPath, request smuggling, prototype pollution, type juggling, HTTP parameter pollution, XSLT, and CSV formula injection.

Full instructions (SKILL.md)

Source of truth, from yaklang/hack-skills.


name: injection-checking description: >- Entry P1 category router for injection testing. Use when routing between XSS, SQLi, SSRF, XXE, SSTI, command injection, and NoSQL injection workflows based on how attacker-controlled input is consumed.

Injection Testing Router

This is the routing entry point when input reaches a dangerous interpreter or execution environment.

After confirming this is an injection-class issue, use it to decide whether it is mainly browser context, database, template engine, server-side requests, XML parsing, or system commands.

When to Use

  • Input reaches HTML, JS, SQL, templates, URL fetchers, XML parsers, or shell
  • You have not yet decided whether to start with XSS, SQLi, SSRF, XXE, SSTI, CMDi, or NoSQL
  • You need to choose the correct deep-topic skill based on input flow

Skill Map

  • XSS Cross Site Scripting
  • SQLi SQL Injection
  • SSRF Server Side Request Forgery
  • XXE XML External Entity
  • SSTI Server Side Template Injection
  • CMDi Command Injection
  • NoSQL Injection
  • Deserialization Insecure
  • JNDI Injection
  • Expression Language Injection
  • CRLF Injection
  • Extra Injection Types (SSI, LDAP, XPath)
  • Request Smuggling
  • Prototype Pollution
  • Type Juggling
  • HTTP Parameter Pollution
  • XSLT Injection
  • CSV Formula Injection

Recommended Flow

  1. First identify the final sink of the input
  2. Then choose the topic skill that best matches that interpreter
  3. Small payload samples and quick triage are merged into each main skill; no extra payload router is needed

Related Categories

  • file-access-vuln