agentic-security:security-sql-injection-warn

Block unsafe SQL string concatenation and enforce parameterized queries during code editing.

73|15|Updated May 6, 2026
One-click install
npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-sql-injection-warn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-security:security-sql-injection-warn
Source: https://github.com/Clear-Capabilities/agentic-security/tree/main/skills/security-sql-injection-warn
Command: npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-sql-injection-warn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents SQL injection by refusing string concatenation and interpolations of user input in queries, guiding developers toward safe parameterized patterns.

Core Features & Use Cases

  • Refuse unsafe string concatenation in SQL queries and template literals.
  • Recommend and demonstrate parameterized query patterns across Node, Python, Prisma, and ORMs.
  • Provide guardrails against NoSQL-like injections and dynamic query construction.

Quick Start

Block SQL injection by refusing string concat.

Frequently Asked Questions about agentic-security:security-sql-injection-warn

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

FAQPage Schema
How do I prevent SQL injection from string concatenation in my code?

Yes, NoSQL injection is covered by applying guardrails against dynamic query construction and NoSQL-like injection patterns. It blocks unsafe query building and enforces safer parameterized alternatives during code editing.

Does this SQL injection check work with Python and Node ORMs like Prisma?

Yes, this SQL injection check works with Node, Python, and ORMs like Prisma. It detects unsafe query construction across multiple languages and recommends the correct parameterized query patterns for each specific framework.

What is the best way to enforce parameterized queries during code review?

The best way to enforce parameterized queries is to use guardrails that automatically refuse string concatenation in SQL queries. This guides developers toward safe patterns by providing canonical commands to scan and fix unsafe code.

How do I scan and fix unsafe SQL query construction?

You can scan and fix unsafe SQL query construction by running canonical setup, scan, and fix commands. These commands identify embedded user input in string concatenations and automatically apply parameterized query guardrails.

Why should I use parameterized queries instead of template literals for database input?

You should use parameterized queries instead of template literals because interpolating user input directly into queries creates SQL injection vulnerabilities. Parameterized queries separate code from data, effectively blocking injection attacks.