input-validation
Skill15 starsChanged 5 months agoCC0-1.0View on GitHub
Reviews input validation and sanitization across the application for injection and malformed-input risks. Use when auditing how untrusted input is handled.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If no target path is given above, review the entire codebase.
- Distinctive: line 55
Create a validation matrix showing each endpoint and its validation status.
- Distinctive: line 75
Prefer minimal, drop-in fix snippets over prose.
- Distinctive: line 77
Do not invent files or functions that aren’t present.
- Distinctive: line 79
Write this into a markdown file and place it in the audits/ folder.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Input Validation
Review all input validation across the application.
Check for:
- SQL Injection vulnerabilities
- Raw SQL queries without parameterization
- Dynamic query building
- Stored procedure calls
- NoSQL Injection (if using MongoDB)
- Unvalidated query operators ($where, $ne, $gt)
- JavaScript execution in queries
- Command Injection
- Child process spawning
- System command execution
- XSS Prevention
- Input sanitization
- Output encoding
- Content-Type headers
- XXE (XML External Entity) attacks
- XML parsing configuration
- File upload handling
- Path Traversal
- File system operations
- Directory listing prevention
- Request validation
- Body size limits
- Parameter pollution
- Type checking
- Required field validation
Create a validation matrix showing each endpoint and its validation status.
Provide:
A structured finding report with the following for each issue:
Title, Severity (Critical/High/Medium/Low), CWE (if applicable), Evidence (file, function, line ranges), and a short Why it matters.
Exploitability notes and, where safe, a minimal PoC or reproduction steps (no real secrets).
Remediation: precise code-level fix or config change (snippets welcome), plus defense-in-depth guidance.
A summary risk score (0–10) and top 3–5 prioritized fixes that reduce risk fastest.
A checklist diff: which items from the “Check for” list are Pass/Fail/Not Applicable.
Constraints & style:
Be concrete and cite exact code locations and identifiers.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- drvoss/everything-copilot-cli★ 49same name
- suhailkakar/the-skills★ 26same name
- YepAPI/skills★ 8same name
- Sagargupta16/agent-recipes★ 4same name
- kimtth/agent-skill-100-lines-or-less★ 2same name
- OpenOps-Studio/vibe-driven-dev★ 1same name
- hereshecodes/secureskills★ 0same name
- jars-demo/jars-skills★ 0same name
- Jinbae10/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use rate-limiting, observability and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
harperaaSkillrate-limiting
Implement rate limiting to prevent brute force attacks, spam, and resource abuse. Use this skill when you need to protect endpoints from automated attacks, prevent API abuse, limit request frequency, or control infrastructure costs. Triggers include "rate limiting", "rate limit", "brute force", "prevent spam", "API abuse", "resource exhaustion", "DoS", "withRateLimit", "too many requests", "429 error".
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
In this repository21 other files it gives its agents.
- api-and-infrastructureSkill
- authentication-flow-reviewSkill
- authorization-implementationSkill
- business-logic-vulnerabilitiesSkill
- code-duplication-detectionSkill
- code-quality-metrics-standardsSkill
- comprehensive-security-reportSkill
- database-securitySkill
- design-pattern-implementationSkill
- error-handling-resilienceSkill
- exception-flow-analysisSkill
- file-handling-business-logicSkill
- initial-security-analysisSkill
- initial-software-design-analysisSkill
- logging-monitoringSkill
- readability-and-namingSkill
- resilience-fault-toleranceSkill
- secrets-management-auditSkill
- session-cookie-securitySkill
- solid-principlesSkill
- testing-implementationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.