injection-checking

Route attacker-controlled input to the appropriate injection testing sub-skill.

5|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Yliken/ai4 --skill injection-checking-yliken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: injection-checking
Source: https://github.com/Yliken/ai4/tree/main/skills/injection-checking
Command: npx skills add https://github.com/Yliken/ai4 --skill injection-checking-yliken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • The Skill acts as a centralized router to dispatch to specialized injection testing skills based on where the attacker-controlled input is consumed (browser context, database queries, template engines, server-side requests, XML parsers, or shell).

  • It references a map of sub-skills including:

    • 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
  • Use Case: When you have input flowing into multiple interpreters, this router decides which specific testing tactic to run next.

Quick Start

Feed an attacker-controlled input and use the router to route it to the appropriate injection testing sub-skill for analysis.

Frequently Asked Questions about injection-checking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which injection testing method to use for attacker-controlled input?

To identify the correct injection testing method, analyze how attacker-controlled input is consumed by the target system. The input flow into browsers, databases, template engines, services, XML parsers, or shell environments determines the specific testing tactic.

What is the best way to route SQLi, XSS, and SSRF testing workflows?

Routing injection testing workflows requires a centralized router to evaluate input flow and dispatch to specialized sub-skills like SQLi, XSS, or SSRF. This ensures precise testing tactics are applied based on the specific interpreter receiving the input.

When do I need to use a router for injection testing?

You need an injection testing router when attacker-controlled input flows into multiple interpreters. It maps the input consumption context to dispatch the correct specialized testing workflow for vulnerabilities like XXE, SSTI, or command injection.

Can I test for NoSQL injection and command injection using the same routing process?

Yes, you can route tests for NoSQL injection and command injection using the same process. The router evaluates the target interpreter consuming the input and dispatches the analysis to the corresponding specialized sub-skill.

How to determine the exact injection context for server-side template injection?

To determine the injection context for server-side template injection, trace how user-controlled data flows into template engines. The router validates this input flow against available sub-skills to engage the precise SSTI testing tactic.

Does this injection testing approach handle XML external entity vulnerabilities?

Yes, this injection testing approach handles XML external entity vulnerabilities. When attacker-controlled input flows into XML parsers, the router identifies this context and dispatches the analysis to the specialized XXE testing sub-skill.