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 skills add louisbrulenaudet/monorepo-template --skill review-zodgit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/review-zod)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-zod"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-zod/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.
<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-zod"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-zod.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.00959 |
| Opus 5 | $0.00033 | $0.00479 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
review-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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Zod
Review Zod usage across contract boundaries (@repo/dtos-common, HTTP routes, SPA clients, queue/webhook payloads) for alignment with current official Zod v4 best practices - schema organization, typing, and parse performance. Your reply must be a plan of suggested changes: concise, actionable, structured - not only prose.
Invocation
Text after the slash command is additional scope/focus (e.g. "dtos-common only", "error formatting") - narrow the review accordingly.
Ground truth (mandatory)
Your pre-trained knowledge of Zod may be outdated (v3 → v4 changed APIs and error internals significantly). Do not draft suggestions from memory alone.
- Resolve "Zod" via the Context7 MCP (
resolve-library-id→query-docs) at v4: top-level APIs,.safeParse/.parsesemantics,z.output/z.inputinference, discriminated unions, registries/metadata features, error customization, tree-shaking/minification notes. - For anything Context7 lacks, use Firecrawl search/scrape restricted to the official domain (
zod.dev) - v4 changelog/migration notes relevant to schemas in this repo. - Version currency: catalog
zodin pnpm-workspace.yaml and installed version vs latest stable; flag any remaining v3-only APIs (e.g. old error-map patterns) in code. - Cite the retrieved source next to every finding; label anything unverifiable as Unverified.
Scope artifacts
- packages/dtos-common/src/ -
api/,rpc/,queue/,webhook/schema folders - Consumers: apps/worker-api/src/routes/ (validation middleware), front-app services decoding responses
- .claude/rules/contracts/ ↔
.cursor/rules/contracts/ownership conventions - Tests asserting schema contracts under
packages/dtos-commonand app tests
Analysis axes
- Single source of truth: every cross-boundary payload has exactly one owning schema in
dtos-common; no shadow re-declarations in apps; enums sourced from@repo/enums-common. - Inference discipline: types derived via
z.infer/z.output(input vs output distinction respected); no hand-written duplicate TS types drifting from schemas. - Boundary coverage: all Hono routes validate request/response payloads; webhook signatures verified before parsing; queue messages validated on consume.
- Schema quality: discriminated unions over boolean flags;
.strict()/.loose()choices deliberate; reusable primitives factored; no runtime-costly transforms on hot paths where a refine suffices. - Errors: consistent error formatting for API responses (no internal details leaked); i18n/custom messages pattern coherent with current v4 APIs.
- Version currency: full v4 adoption (no compat shims); new capabilities worth adopting noted.
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.
- 12d ago First seen · 62 lines · 66 tokens per session scan A 14e388d3d2e2
review-zod is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 66 tokens to every session and 959 once invoked, about $0.0003 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
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
bfl-api
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
api-design-reviewer
Use when reviewing API designs for consistency, usability, versioning, error semantics, security, backward compatibility, and developer experience before implementation or release.
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-perf-review
Review Kafka producer and consumer performance configurations in both the live cluster (via Lenses MCP) and the codebase. Flags un-tuned defaults, anti-patterns and missing best practices. Use when user says "review Kafka performance", "check producer configs", "tune Kafka settings" or asks about throughput, batching…