web-sqli-validation

Validates scoped SQL injection hypotheses through reproducible HTTP response differentials.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill web-sqli-validation-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-sqli-validation
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/web-sqli-validation
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill web-sqli-validation-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confirming a suspected SQL injection vulnerability requires more than a single anomalous response; this Skill turns a raw hypothesis into evidence-backed findings by comparing paired control requests against SQL-semantic variants and measuring reproducible response differentials. ## Core Features & Use Cases - Baseline Establishment: Measures repeatable baseline response ranges before mutating parameters, so noise is quantified rather than guessed. - Paired Differential Testing: Compares control requests with SQL-semantic variants at low request frequency, requiring every claimed differential to reproduce against a matched control. - Structured Classification: Returns evidence-linked observations with oracle type, confidence, blockers, and attack-graph relation updates conforming to the worker-result-v1 schema. - Use Case: A supervisor agent assigns capability web.sqli.validate for a specific endpoint and parameter; the worker verifies scope anchors, runs differential probes, and returns a classified result that updates the multi-hop attack graph. ## Quick Start Assign this worker the web.sqli.validate capability with a scoped endpoint, parameter, and baseline evidence, then ask it to validate the SQL injection hypothesis and return the classified result.

Frequently Asked Questions about web-sqli-validation

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

FAQPage Schema
How do I validate a SQL injection vulnerability without false positives?

Establish repeatable baseline response ranges first, then compare paired control requests against SQL-semantic variants at low frequency. A finding is only confirmed when every claimed differential reproduces against a matched control, separating real injection behavior from noise.

What is differential-based SQL injection testing?

Differential testing sends paired requests where only the SQL semantics of one parameter differ, then compares responses. Consistent differences between control and variant responses indicate the parameter reaches a SQL parser, forming the oracle for classification.

Can this skill test any endpoint I point it at?

No. It only operates within an assigned scope: the endpoint, parameter, baseline evidence, and scope snapshot must match the assigned Case revision anchors before testing begins. Out-of-scope targets are rejected by the verification step.

What output does the SQL injection validation produce?

It returns a result conforming to the worker-result-v1 JSON schema, echoing the skill ID, version, and digest through task anchors. The result states the classification oracle, confidence level, blockers, and relation updates for the attack graph.

Why does SQL injection validation require low request frequency?

Low-frequency probing reduces the risk of triggering rate limits, WAF blocks, or service disruption on the target. It also keeps baseline measurements stable so response differentials reflect injection behavior rather than server throttling artifacts.