input-validation-checker

Audit codebases for untrusted inputs lacking allowlist-first validation schemas.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill input-validation-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: input-validation-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/security/input-validation-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill input-validation-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of critical security vulnerabilities caused by untrusted user inputs crossing trust boundaries without proper validation, which is the root cause of injection attacks, mass assignment, denial of service, and file upload RCE flaws.

Core Features & Use Cases

  • Cross-Channel Input Auditing: Scans all input sources including HTTP bodies, query parameters, headers, file uploads, WebSocket frames, message queues, and environment variables across 7 supported programming languages.
  • 2026 Best Practice Enforcement: Validates adherence to allowlist-first schemas, fail-closed validation, Unicode normalization, and schema-driven validation rules.
  • Compliance-Ready Reporting: Maps all findings to OWASP Top 10 and CWE identifiers, with clear remediation guidance and integration with SAST tools for corroboration. Use case: For a fintech web app, it flags unvalidated payment request bodies that could allow mass assignment of transaction amounts.

Quick Start

Use the input-validation-checker skill to audit all API endpoints in your current project for missing input validation and generate a prioritized security report.

Frequently Asked Questions about input-validation-checker

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

FAQPage Schema
How do I audit my codebase for missing input validation across all input channels?

To audit codebases for missing input validation, scan all input channels including HTTP request bodies, query parameters, headers, file uploads, WebSocket frames, message queues, and environment variables to identify untrusted inputs crossing trust boundaries without typed, allowlist-first validation schemas.

What is the best way to prevent injection attacks caused by unvalidated user inputs?

Preventing injection attacks caused by unvalidated user inputs requires enforcing allowlist-first schemas, fail-closed validation, and Unicode normalization to ensure untrusted data cannot cross trust boundaries without proper schema-driven validation rules.

How do I map input validation flaws to OWASP Top 10 and CWE identifiers?

Mapping input validation flaws to OWASP Top 10 and CWE identifiers generates compliance-ready security reports with clear remediation guidance for untrusted user inputs crossing trust boundaries without proper validation across all supported input channels.

Does this input validation checker support SAST tool integration for critical severity findings?

Yes, this input validation checker integrates with SAST tools to corroborate critical severity findings, ensuring identified untrusted user input flaws are cross-verified before generating a prioritized security report mapped to OWASP Top 10 and CWE identifiers.

Can I scan WebSocket frames and message queues for unvalidated inputs?

Yes, you can scan WebSocket frames and message queues for unvalidated inputs alongside HTTP request bodies, query parameters, headers, file uploads, and environment variables across 7 supported programming languages to ensure full input channel coverage.

What are the limitations of relying on schema validation for injection prevention?

Relying on schema validation for injection prevention enforces typed, allowlist-first validation schemas, fail-closed validation, and Unicode normalization on untrusted inputs, but requires SAST tool integration to corroborate critical severity findings across all input channels.