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/pymodel/react-frontend-skills/zodnpx skills add PyModel/react-frontend-skills --skill zodgit clone --depth 1 https://github.com/PyModel/react-frontend-skillsWhat 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.00059 | $0.01327 |
| Opus 5 | $0.00030 | $0.00664 |
| Sonnet 5 | $0.00012 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
zod 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 3d 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.
This is a copy
92% identical to zod — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zod Best Practices
Comprehensive schema validation guide for Zod 4 in TypeScript applications. Contains 43 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new Zod schemas
- Choosing between parse() and safeParse()
- Implementing type inference with z.infer
- Handling validation errors for user feedback
- Composing complex object schemas
- Using refinements and transforms
- Optimizing bundle size and validation performance
- Reviewing Zod code for best practices
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Schema Definition | CRITICAL | schema- |
| 2 | Parsing & Validation | CRITICAL | parse- |
| 3 | Type Inference | HIGH | type- |
| 4 | Error Handling | HIGH | error- |
| 5 | Object Schemas | MEDIUM-HIGH | object- |
| 6 | Schema Composition | MEDIUM | compose- |
| 7 | Refinements & Transforms | MEDIUM | refine- |
| 8 | Performance & Bundle | LOW-MEDIUM | perf- |
Quick Reference
1. Schema Definition (CRITICAL)
schema-use-primitives-correctly- Use correct primitive schemas for each typeschema-use-unknown-not-any- Use z.unknown() instead of z.any() for type safetyschema-avoid-optional-abuse- Avoid overusing optional fieldsschema-string-validations- Apply string validations at schema definitionschema-use-enums- Use enums for fixed string valuesschema-coercion-for-form-data- Use coercion for form and query data
2. Parsing & Validation (CRITICAL)
parse-use-safeparse- Use safeParse() for user inputparse-async-for-async-refinements- Use parseAsync for async refinementsparse-handle-all-issues- Handle all validation issues not just firstparse-validate-early- Validate at system boundariesparse-avoid-double-validation- Avoid validating same data twiceparse-never-trust-json- Never trust JSON.parse output
What ships with it
46 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 9.9 KB
- metadata.json 1.9 KB
- references/_sections.md 2.2 KB
- references/compose-intersection.md 3.5 KB
- references/compose-lazy-recursive.md 3.5 KB
- references/compose-pipe.md 3.3 KB
- references/compose-preprocess.md 3.6 KB
- references/compose-shared-schemas.md 3.2 KB
- references/error-avoid-throwing-in-refine.md 3.3 KB
- references/error-custom-messages.md 3.7 KB
- references/error-i18n.md 4.0 KB
- references/error-path-for-nested.md 3.7 KB
- references/error-use-flatten.md 2.2 KB
- references/object-discriminated-unions.md 3.9 KB
- references/object-extend-for-composition.md 3.3 KB
- references/object-optional-vs-nullable.md 3.6 KB
- references/object-partial-for-updates.md 3.5 KB
- references/object-pick-omit.md 3.7 KB
- references/object-strict-vs-strip.md 2.0 KB
- references/parse-async-for-async-refinements.md 3.0 KB
- references/parse-avoid-double-validation.md 3.2 KB
- references/parse-handle-all-issues.md 3.3 KB
- references/parse-never-trust-json.md 3.1 KB
- references/parse-use-safeparse.md 2.7 KB
- references/parse-validate-early.md 3.3 KB
- references/perf-arrays.md 3.9 KB
- references/perf-avoid-dynamic-creation.md 2.5 KB
- references/perf-cache-schemas.md 3.0 KB
- references/perf-lazy-loading.md 3.5 KB
- references/perf-zod-mini.md 3.1 KB
- references/refine-add-path.md 3.7 KB
- references/refine-catch.md 3.7 KB
- references/refine-defaults.md 3.6 KB
- references/refine-transform-coerce.md 3.4 KB
- references/refine-vs-superrefine.md 4.0 KB
- references/schema-avoid-optional-abuse.md 2.6 KB
- references/schema-coercion-for-form-data.md 2.9 KB
- references/schema-string-validations.md 3.0 KB
- references/schema-use-enums.md 2.7 KB
- references/schema-use-primitives-correctly.md 2.0 KB
- references/schema-use-unknown-not-any.md 2.2 KB
- references/type-branded-types.md 3.0 KB
- references/type-enable-strict-mode.md 2.9 KB
- references/type-export-schemas-and-types.md 3.0 KB
- references/type-input-vs-output.md 3.1 KB
- references/type-use-z-infer.md 2.9 KB
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.
- 3d ago First seen · 126 lines · 59 tokens per session scan A 0917c5406b53
zod is a skill published in the GitHub repository PyModel/react-frontend-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 59 tokens to every session and 1,327 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to zod, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
type-safety
TypeScript type safety conventions for the Playwright scaffold — the "no any" rule, Zod 4 schema patterns (z.strictObject, top-level validators like z.uuid / z.email / z.url / z.int / z.enum), schemas built directly from the documented OpenAPI / Swagger contract (response envelope spelled out per endpoint), type…
enums
TypeScript enum conventions for the Playwright scaffold — PascalCase enum names, SCREAMINGSNAKECASE members, location rules for app-specific (enums/{area}/) vs shared/utility (enums/util/) constants, and the rules for adding or extending enums. Use when adding a new API endpoint path, UI message, role, storage-state…
refactor-values
Safe refactoring workflow for enum values, enum keys, and static test data in test-data/static/.ts — mandatory impact analysis, cascading updates, and verification. Use BEFORE changing any enum member's string value (ApiEndpoints., Messages., Roles, StorageStatePaths), renaming any enum key, or editing any existing…
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
typescript-best-practices
Enforces TypeScript best practices and modern patterns.