Security Injection Specialist

Traces untrusted input to interpreter sinks to detect SQL, command, XSS, SSRF, and SSTI injection vulnerabilities.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill security-injection-specialist-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Security Injection Specialist
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/agents/security-injection
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill security-injection-specialist-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss injection vulnerabilities because tracing untrusted data from input sources to dangerous interpreter sinks across large diffs is tedious and error-prone. This Skill performs deep data-flow analysis to catch SQL, command, XSS, SSRF, and SSTI injection flaws before they ship. ## Core Features & Use Cases - Source-to-Sink Tracing: Identifies input sources (request params, headers, environment variables) and traces them to interpreter sinks (SQL queries, shell commands, HTML output, template rendering, outbound HTTP requests). - Five Injection Classes: Classifies findings as SQL, Command, XSS, SSRF, or SSTI with P0-P3 severity ratings and concrete fix recommendations. - Parallel Large-Diff Analysis: Spawns subagents to trace different file groups in parallel for diffs over 500 lines, then merges findings. - Use Case: During a security review of a pull request, the Skill detects that a user-controlled URL parameter flows directly into an outbound HTTP request, flags it as an SSRF finding with file and line location, and recommends an allowlist-based fix. ## Quick Start Ask the security reviewer to run an injection analysis on the changed files in this pull request and report any SQL, command, XSS, SSRF, or SSTI findings with severity ratings.

Frequently Asked Questions about Security Injection Specialist

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

FAQPage Schema
How do I detect SQL injection vulnerabilities in a code review?▼

Trace untrusted input sources like request params and body fields to SQL query sinks. Flag direct string concatenation or template interpolation into queries as P0/P1 findings, and mark parameterized or prepared statements as safe.

What injection types does this security review cover?▼

The analysis covers five injection classes: SQL injection, command injection via exec or system calls, XSS through innerHTML or unsafe template filters, SSRF via user-controlled URLs in HTTP requests, and SSTI via template rendering of user input.

How are injection findings classified and reported?▼

Each finding includes the injection type, severity from P0 to P3, file and line location, the input source, the interpreter sink, a brief data-flow trace, and a recommended safe-pattern fix. Clean reviews return a clear no-findings message.

Can injection analysis handle large pull request diffs?▼

Yes, for diffs over 500 lines the analysis spawns parallel subagents to trace different file groups and merges their findings. Files containing interpreter sinks are prioritized over pure data or configuration files.

When is sanitization considered adequate against injection?▼

Sanitization is checked against known safe and unsafe pattern pairs before data reaches a sink. Parameterized queries and prepared statements are treated as safe, while incomplete escaping or blacklist filters on the flow path are flagged for review.