Zod is a TypeScript library that checks whether data matches defined schemas while also deriving corresponding static types. It is used by developers to validate data at runtime in TypeScript applications.
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/colinhacks/zod/triagenpx skills add colinhacks/zod --skill triagegit clone --depth 1 https://github.com/colinhacks/zodWrote 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/colinhacks/zod/triage)<a href="https://agentmods.dev/skills/colinhacks/zod/triage"><img src="https://agentmods.dev/badge/skills/colinhacks/zod/triage.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.1 | $0.00239 | $0.05955 |
| Opus 5 | $0.00120 | $0.02978 |
| Sonnet 5 | $0.00048 | $0.01191 |
| Haiku 4.5 | $0.00024 | $0.00596 |
Grade A, and why
triage 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 6d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigating issues and PRs
Produce a write-up a maintainer can act on without re-reading the thread. The durable deliverable is always a file on disk — sweeps span many sessions and agents, so anything living only in a transcript is lost. But the file is not what the user reads first: your final chat message is, and for most tickets it is the only thing they will ever read. Both matter, and ## Reporting back below is not optional.
Read-only on GitHub. Never comment, label, assign, close, review, approve, or merge unless the user explicitly asks in this session. You are forming an opinion, not publishing one. Drafting the close comment described below is part of forming it — writing the text is required, sending it is not yours to do.
Where things live
Everything goes under .triage/ in the root repo, which is gitignored — write freely, it never shows up in git status.
.triage/
index.md # the original issue sweep index — hand-maintained prose, still the canonical issue queue
issues/index.md # generated from frontmatter by reindex.mjs
issues/<N>/results.md # the write-up; scratch files live beside it
prs/index.md # generated
prs/<N>/results.md
advisories/<GHSA-ID>/results.md # draft security advisories from the Security tab
signal-report.md # generated by scripts/triage-signal.ts — ranks the open backlog
One directory per ticket, named by bare GitHub number (no leading zeros, no issue-/pr- prefix) — or by bare GHSA id for an advisory. results.md is the write-up. Everything else you need — repro scripts, a saved gh pr diff, test fixtures, benchmark output, notes — goes in that same directory. Name scratch files descriptively (repro.ts, diff.patch, bench-before.txt); there is no naming rule beyond not colliding with results.md.
For an issue repro, pnpm dev .triage/issues/<N>/repro.ts from the root repo works directly.
A repro must sit inside the checkout it is testing, because module resolution walks up from the file, not from the cwd — a script under .triage/ cannot resolve zod from a PR worktree. Keep the canonical copy in the ticket directory and copy it in to run: cp .triage/prs/<N>/repro.ts <worktree>/repro-<N>.ts. That is also what lets you run the identical file against both main and the PR and diff the output, which is the cheapest way to characterize a behavior change. For a probe needing GC or other flags, skip pnpm dev and invoke node directly: node --expose-gc --conditions=@zod/source --import tsx repro-<N>.ts.
What ships with it
1 file 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.
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.
- 6d ago First seen · 286 lines · 239 tokens per session scan A e4bb0663d2d5
triage is a skill published in the GitHub repository colinhacks/zod (43,847 stars, last pushed today), licensed MIT. It adds 239 tokens to every session and 5,955 once invoked, about $0.0012 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
Zod
Zod 4.x — TypeScript-first schema validation with static type inference. Primitives, strings, objects, refinements.
zod
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, v3→v4 migration, and testing schemas with Jest or Vitest. Baseline: zod ^4.3.0. Triggers…
fp-pack
Use when working in projects that use fp-pack; follow pipe, SideEffect, and curry guidelines.
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…
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).