Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/apisec-inc/apisec-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/apisec-inc/apisec-skills/input-validation)<a href="https://agentmods.dev/rules/apisec-inc/apisec-skills/input-validation"><img src="https://agentmods.dev/badge/rules/apisec-inc/apisec-skills/input-validation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/apisec-inc/apisec-skills/input-validation"><img src="https://agentmods.dev/badge/rules/apisec-inc/apisec-skills/input-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00229 | $0.00229 |
| Opus 5.5 | $0.00092 | $0.00092 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
input-validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 23d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Input validation rule
All user-supplied input (path params, query params, request body, headers) must pass through a validation layer before being used in any logic, query, or response.
Never pass req.params, req.body, req.query, or request.data directly to a database query, shell command, file path, or template without validation.
Recommended validation approach per framework:
- Express/Node: zod or joi schema validation
- FastAPI: Pydantic models with field constraints
- Django: DRF serializers with explicit field validation
- Spring: @Valid with Bean Validation annotations
- Go: manual struct validation or validator library
When generating an endpoint, always include the validation layer. If the user hasn't defined a schema yet, generate a placeholder schema with the correct structure.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 23d ago Changed 3d1d11a8fe8d
- 1mo ago First seen · 26 lines · 229 tokens per session scan A 0b13aa90b196
input-validation is a cursor rule published in the GitHub repository apisec-inc/apisec-skills (21 stars, last pushed 23d ago), licensed MIT. It adds 229 tokens to every session, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
patchman
Patchman defensive security review defaults.
project-memory
This rule guides recording project events and decisions in projectmem.
mcpnuke-development
Core mcpnuke development standards and superpowers workflow integration.
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.