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.
npx agentmods add agents/continuedev/continue/input-validationgit clone --depth 1 https://github.com/continuedev/continueWhat 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 | $0.00013 | $0.00424 |
| Opus 5 | $0.00006 | $0.00212 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 2d 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 Check
Review this pull request for input validation quality. The most common user issues in this codebase stem from malformed API keys, blank inputs, and missing configuration values that produce confusing downstream errors.
What to Check
-
API keys and secrets - Any code that accepts API keys, tokens, or credentials should:
- Reject obviously invalid values (empty strings, whitespace-only, placeholder text like "your-api-key-here")
- Validate format where possible (e.g., OpenAI keys start with
sk-, Anthropic keys start withsk-ant-) - Provide a clear error message before making a network request with a bad key
-
Configuration values - New or modified config parsing should:
- Validate required fields are present and non-empty
- Validate types (e.g., numbers are actually numbers, URLs are valid URLs)
- Provide clear error messages that name the specific field and expected format
- Not crash the entire config loading process for a single invalid value
-
User text inputs - New or modified UI inputs should:
- Handle empty/whitespace-only submissions gracefully
- Sanitize inputs that will be used in file paths, URLs, or shell commands
- Not allow submission of invalid data that will fail silently later
-
URL and endpoint validation - When users provide custom URLs (e.g., for self-hosted LLM endpoints):
- Validate URL format
- Handle missing protocol (add
https://if missing) - Provide feedback before attempting connection
What NOT to Flag
- Internal function parameters (trust internal callers)
- Test inputs
- Validation that already exists and is working correctly
- Configuration values with sensible defaults that don't require user input
Scope
Only review files changed in this PR. If you find missing validation, add it directly. Keep fixes minimal and focused. If no user-facing input handling was changed, do nothing.
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.
- 2d ago First seen · 46 lines · 13 tokens per session scan A 9f33469fe5ef
Input Validation is an agent published in the GitHub repository continuedev/continue (35,702 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 424 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.