injection-checking

Routes injection testing workflows across XSS, SQLi, SSRF, XXE, SSTI, and command injection sinks.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/hanmujun/hanmujun-agent-public --skill injection-checking-hanmujun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: injection-checking
Source: https://github.com/hanmujun/hanmujun-agent-public/tree/main/skill-library/injection-checking
Command: npx skills add https://github.com/hanmujun/hanmujun-agent-public --skill injection-checking-hanmujun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When attacker-controlled input reaches a dangerous interpreter, testers often struggle to decide which injection class applies and which deep-dive workflow to follow. This Skill acts as a category router that maps input sinks to the correct injection testing topic. ## Core Features & Use Cases - Sink-Based Routing: Identifies whether input flows into HTML/JS, SQL, template engines, URL fetchers, XML parsers, or shell commands, then points to the matching deep-topic skill. - Comprehensive Skill Map: Links to 18 specialized injection skills including XSS, SQLi, SSRF, XXE, SSTI, CMDi, NoSQL, JNDI, CRLF, prototype pollution, and request smuggling. - Extra Injection Reference: Covers less common types such as SSI, LDAP, XPath, LaTeX injection, encoding bypasses, and PHP variable modification with detection probes and payloads. - Use Case: During a CTF web challenge, you find a login form reflecting input. Use this router to trace the sink, determine it is an LDAP-backed filter, and jump to the LDAP injection methodology with authentication bypass payloads. ## Quick Start Ask the agent to load the injection-checking skill and classify which injection type applies to the user input found in the current challenge.

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 type a web input is vulnerable to?▼

Trace the final sink of the input first: HTML or JavaScript context indicates XSS, database queries indicate SQLi or NoSQL, URL fetchers indicate SSRF, XML parsers indicate XXE or XPath, and shell calls indicate command injection. Then select the matching deep-topic skill for that interpreter.

What injection types does this router cover?▼

It routes to 18 specialized skills including XSS, SQLi, SSRF, XXE, SSTI, command injection, NoSQL, deserialization, JNDI, expression language, CRLF, request smuggling, prototype pollution, type juggling, HTTP parameter pollution, XSLT, and CSV formula injection, plus an extra reference for SSI, LDAP, XPath, and LaTeX injection.

How do I test for LDAP injection in a login form?▼

Inject filter metacharacters like admin)(&) as the username to force the LDAP filter to evaluate true, or use wildcard extraction like (password=a*) to enumerate credentials character by character. Null byte truncation can skip password checks in some OpenLDAP setups.

Can blind XPath injection extract data when results are not visible?▼

Yes. Use boolean probes with string-length and substring functions to map the XML structure, count nodes, discover element names, and extract values character by character, such as ' or substring(//user[1]/password,1,1)='s' or '1'='2.

When should I use a deep-topic injection skill instead of this router?▼

Use this router only when you have confirmed an injection-class issue but have not decided the specific type. Once the sink is identified, switch directly to the matching deep-topic skill, which contains merged payload samples and triage steps.