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/security-advisorynpx skills add colinhacks/zod --skill security-advisorygit 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/security-advisory)<a href="https://agentmods.dev/skills/colinhacks/zod/security-advisory"><img src="https://agentmods.dev/badge/skills/colinhacks/zod/security-advisory.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.00000 | $0.02217 |
| Opus 5 | $0.00000 | $0.01108 |
| Sonnet 5 | $0.00000 | $0.00443 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
security-advisory 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triaging a draft security advisory
Advisories are not issues with a scarier label. Four things differ, and each one changes the order you work in:
- The report is private, and private in both directions — see
## Privacy cuts both ways. - The burden of proof is on the reporter. Most submissions are scanner output or a rediscovery of intended behavior. A plausible writeup is not evidence.
- The fix lands before the comment exists. See
## Land the fix first. This is the rule most often broken and the one that wastes the most of Colin's time. - Real defect and publishable vulnerability are different questions. See
## Publish or decline.
Everything in the triage skill about where files live, results.md frontmatter, close-comment voice, and reporting back in chat still applies. This skill replaces only its ## Investigating a draft advisory section.
Never accept, publish, decline, or comment on an advisory. The write-up and the drafted note are the deliverables; the disposition is Colin's. Landing a fix is a code change and follows the repo's normal rules; publishing a CVE is not, and is never yours.
Reading the queue
gh api repos/colinhacks/zod/security-advisories --paginate \
--jq '.[] | select(.state=="triage") | [.ghsa_id, .severity, .summary] | @tsv'
gh api repos/colinhacks/zod/security-advisories/<GHSA-ID> --jq '.description' # full report + PoC
Write-ups go to .triage/advisories/<GHSA-ID>/results.md, scratch files beside them. Frontmatter swaps number: for ghsa: and adds severity_claimed: (what the reporter asserted) next to severity_actual: (yours, or none).
verdict is one of valid, not-a-vulnerability, already-fixed, duplicate (with duplicate_of:), needs-reporter-info, needs-maintainer-decision. Add fixed_by: / fix_pr: once a fix lands, and disposition_recommended: when you have a publish-or-decline opinion. Keep verdict describing the defect and disposition_recommended describing what to do about it — do not let a decline quietly rewrite a real finding as not-a-vulnerability.
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 · 83 lines · 0 tokens per session scan A 0dfcfb4e16ef
security-advisory is a skill published in the GitHub repository colinhacks/zod (43,838 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,217 tokens. 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.
agent-host-e2e-tests
Use when writing, recording, updating, validating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a…