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 instructions/anivar/zod-skill/agents-mdgit clone --depth 1 https://github.com/anivar/zod-skillWrote 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/instructions/anivar/zod-skill/agents-md)<a href="https://agentmods.dev/instructions/anivar/zod-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/anivar/zod-skill/agents-md.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.04602 | $0.04602 |
| Opus 5 | $0.02301 | $0.02301 |
| Sonnet 5 | $0.00920 | $0.00920 |
| Haiku 4.5 | $0.00460 | $0.00460 |
Grade A, and why
zod-skill AGENTS.md 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 4d 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 — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zod v4 — Complete Guide
This document is for AI agents and LLMs to follow when writing, reviewing, or debugging Zod schemas. It compiles all rules and references into a single executable guide.
Baseline: zod ^4.0.0 with TypeScript ^5.5
Abstract
Zod is a TypeScript-first schema validation library for runtime type checking at system boundaries — API input, form data, environment variables, external services. Use z.infer<typeof Schema> for type extraction, safeParse() for validation, and composition methods (.pick(), .omit(), .partial()) to derive schema variants. Zod v4 introduces breaking changes to string formats, enums, error handling, and recursive types. This guide also covers architectural placement (where to parse), schema organization, versioning strategy, and production observability.
Table of Contents
- Parsing & Type Safety — CRITICAL
- Schema Design — CRITICAL
- Refinements & Transforms — HIGH
- Error Handling — HIGH
- Performance & Composition — MEDIUM
- v4 Migration — MEDIUM
- Advanced Patterns — MEDIUM
- Architecture & Boundaries — CRITICAL/HIGH
- Observability — HIGH/MEDIUM
1. Parsing & Type Safety
Impact: CRITICAL
Rule: Use safeParse() for User Input
parse() throws on invalid input. Use safeParse() which returns a discriminated result.
// INCORRECT — try/catch is verbose and catches unrelated errors
try {
const user = UserSchema.parse(data)
} catch (e) {
if (e instanceof z.ZodError) { ... }
}
// CORRECT — discriminated union result
const result = UserSchema.safeParse(data)
if (!result.success) {
console.log(result.error.issues)
} else {
console.log(result.data)
}
Use parse() only for internal data that should never be invalid (config, constants).
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.
- 4d ago First seen · 654 lines · 4,602 tokens per session scan A 13bc5e438148
zod-skill AGENTS.md is an instructions file published in the GitHub repository anivar/zod-skill (21 stars, last pushed 27d ago), licensed MIT. It adds 4,602 tokens to every session, about $0.0230 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 instructions, from other repositories
redux-saga-skill AGENTS.md
Instructions for anivar/redux-saga-skill, covering redux-saga — complete guide, abstract, 1. effects & yielding, rule: always yield effects and rule: use call() for async functions.
developer-docs-framework AGENTS.md
AGENTS.md instructions for anivar/developer-docs-framework, covering tech docs, when to use this skill, foundational frameworks, rule categories by priority and quick reference.
agentic-playwright enums.instructions.md
Instructions for idavidov13/agentic-playwright, covering enums, critical, file locations, instructions and phase 1: decide if the value belongs in an enum.
agentic-playwright refactor-values.instructions.md
Instructions for idavidov13/agentic-playwright, covering refactoring enum values and static test data, critical, instructions, phase 1: find all consumers before touching anything and find all usages of the enum key.
latex-arxiv-SKILL AGENTS.md
Instructions for appautomaton/latex-arxiv-SKILL, covering agents.md, workflow (issue‑driven) and non‑negotiable rules.
jest-skill AGENTS.md
Instructions for anivar/jest-skill, covering jest — complete guide, abstract, 1. mock design, rule: clearallmocks vs resetallmocks vs restoreallmocks and rule: always restore jest.spyon.