injection-checking

Routes attack input to the appropriate specialized testing workflow based on sink type.

11|4|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/sayseven7/frameseven --skill injection-checking-sayseven7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: injection-checking
Source: https://github.com/sayseven7/frameseven/tree/main/internal/mcp/skills/injection-checking
Command: npx skills add https://github.com/sayseven7/frameseven --skill injection-checking-sayseven7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly classify injection-related findings so you can choose the correct testing path instead of guessing between browser, database, template, XML, request, or command execution sinks.

Core Features & Use Cases

  • Injection routing: Identifies whether the issue belongs to XSS, SQL injection, SSRF, XXE, SSTI, command injection, NoSQL injection, or related categories.
  • Sink-based triage: Focuses on how attacker-controlled input is consumed so the next step matches the actual interpreter or execution context.
  • Deep-topic handoff: Directs you to specialized skills for common injection families and related edge cases such as CRLF, request smuggling, prototype pollution, and LDAP or XPath injection.
  • Use case: When a parameter is reflected in a database query or template engine, use this Skill to decide the right exploit-testing workflow before running deeper checks.

Quick Start

Use the injection-checking skill to inspect the input sink and route the issue to the most appropriate injection testing workflow.

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 vulnerability type I am dealing with during triage?

Identify the final sink where attacker-controlled input is consumed to classify the injection type. This routing process matches the issue to the correct testing workflow based on whether input reaches browsers, databases, templates, URL fetchers, XML parsers, or shell interpreters.

What is the best way to route an injection finding to the correct testing workflow?

The best way to route an injection finding is to inspect the input sink and determine the execution context. This skill directs you to specialized testing workflows for XSS, SQLi, SSRF, XXE, SSTI, command injection, and NoSQL injection based on the specific interpreter reached.

How do I test a parameter reflected in a template engine or database query?

To test a reflected parameter, identify the consuming interpreter to select the matching deep-topic skill. If input reaches a template engine, route to SSTI testing; if it reaches a database query, route to SQL injection testing workflows.

Does this injection triage process cover edge cases like request smuggling and prototype pollution?

Yes, the injection triage process covers edge cases including CRLF, request smuggling, prototype pollution, and LDAP or XPath injection. It directs these findings to specialized skills for common injection families and related edge cases.

When do I need to identify the final sink before running deeper injection checks?

You need to identify the final sink before deeper checks whenever attacker-controlled input reaches an interpreter. This ensures the next step matches the actual execution context, preventing guessing between browser, database, template, XML, request, or command execution sinks.