zod: Skill for Claude Code

.claude/skills/security-advisory/SKILL.md

security-advisory is a skill for Claude Code from colinhacks/zod. It costs 0 tokens per session (2,223 once invoked), scanned A, original, MIT.

Guidance for reviewing a private security advisory, which is a report of a possible software vulnerability, in the Zod project.

In plain words
What is it for?
Use it to investigate draft advisories, check the evidence, prepare a write-up, and document a possible fix without accepting, declining, publishing, or commenting on the report.
Why use it?
It separates unverified reports from confirmed defects and keeps private security information handled appropriately. It also explains that the fix should be prepared before writing the response or deciding whether the report can be published.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is colinhacks/zod's own configuration. It tells Claude Code how to work on zod itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zod configures →

About the project

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.

colinhacks/zod · 44,202 stars · on GitHub · zod.dev

Reuse

Borrowing it

Nothing to install: this file belongs to colinhacks/zod. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/colinhacks/zod/main/.claude/skills/security-advisory/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/colinhacks/zod

Made for: Claude Code.

Wrote 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.

agentmods badge for security-advisory

README.md
[![agentmods](https://agentmods.dev/badge/skills/colinhacks/zod/security-advisory/github.svg)](https://agentmods.dev/skills/colinhacks/zod/security-advisory)
Your own site
<a href="https://agentmods.dev/skills/colinhacks/zod/security-advisory"><img src="https://agentmods.dev/badge/skills/colinhacks/zod/security-advisory/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-advisory

Your own site · 80×15
<a href="https://agentmods.dev/skills/colinhacks/zod/security-advisory"><img src="https://agentmods.dev/badge/skills/colinhacks/zod/security-advisory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02223
Opus 5.5 $0.00000 $0.00889
Sonnet 5.5 $0.00000 $0.00445
Haiku 4.5 $0.00000 $0.00222

Measured 1mo ago against content hash 2e104a87bb54, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/security-advisory/SKILL.md · 83 lines

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.

Read the full file on GitHub · 83 lines

Changes

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.

  1. 1mo ago Changed 2e104a87bb54
  2. 1mo ago Changed d48a6c64422e
  3. 1mo ago First seen · 83 lines · 0 tokens per session scan A 0dfcfb4e16ef

Subscribe to this mod's changes

security-advisory is a skill published in the GitHub repository colinhacks/zod (44,202 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,223 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.