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 skills/porcupine-md/jonggrang/input-validationnpx skills add porcupine-md/jonggrang --skill input-validationgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/skills/porcupine-md/jonggrang/input-validation)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/input-validation"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/input-validation.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00843 |
| Opus 5 | $0.00010 | $0.00421 |
| Sonnet 5 | $0.00004 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Everything from External Sources
// Every request body, query param, and path param is untrusted input.
// Validate at the boundary before it touches your domain logic.
Zod Schema Patterns
import { z } from 'zod';
// Base schemas (reusable)
const EmailSchema = z.string().email().max(255).toLowerCase().trim();
const PasswordSchema = z.string().min(8).max(128);
const UUIDSchema = z.string().uuid();
// Request body schema
const CreateUserSchema = z.object({
email: EmailSchema,
password: PasswordSchema,
name: z.string().min(1).max(100).trim(),
role: z.enum(['admin', 'user', 'viewer']).default('user'),
});
// Query params (all strings from URL, need coercion)
const PaginationSchema = z.object({
page: z.coerce.number().int().min(1).default(1),
limit: z.coerce.number().int().min(1).max(100).default(20),
sortBy: z.enum(['createdAt', 'name', 'email']).default('createdAt'),
sortDir: z.enum(['asc', 'desc']).default('desc'),
});
// Path params
const UserParamsSchema = z.object({
id: UUIDSchema,
});
Middleware Approach (Express)
// Generic validation middleware
function validate<T extends z.ZodType>(schema: T, source: 'body' | 'query' | 'params') {
return (req: Request, res: Response, next: NextFunction) => {
const result = schema.safeParse(req[source]);
if (!result.success) {
return res.status(400).json({
error: {
code: 'VALIDATION_ERROR',
message: 'Invalid input',
fields: result.error.flatten().fieldErrors,
},
});
}
req[source] = result.data; // replace with parsed/coerced data
next();
};
}
// Usage
router.post('/users',
validate(CreateUserSchema, 'body'),
asyncHandler(async (req, res) => {
const { email, password, name, role } = req.body; // already validated
const user = await userService.create({ email, password, name, role });
res.status(201).json(user);
})
);
Security Checklist
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.
- 5d ago First seen · 119 lines · 20 tokens per session scan A c22b650ad39f
input-validation is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 843 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…