A pre-implementation review of a specification, meaning a written description of planned work. It checks alignment with the project, feasibility, risks, completeness, trade-offs, and recommendations.

Reviewing feature specifications against an existing codebase and deciding whether they are ready to build.

It finds unclear requirements and structural problems before implementation begins, reducing the chance of divergent interpretations or costly rework.

vet-spec — Command for Claude Code by sergeyklay

Install

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.

Clone the repo

git clone --depth 1 https://github.com/sergeyklay/.agents

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sergeyklay/.agents/vet-spec/github.svg)](https://agentmods.dev/commands/sergeyklay/.agents/vet-spec)

Your own site

<a href="https://agentmods.dev/commands/sergeyklay/.agents/vet-spec"><img src="https://agentmods.dev/badge/commands/sergeyklay/.agents/vet-spec/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sergeyklay/.agents/vet-spec"><img src="https://agentmods.dev/badge/commands/sergeyklay/.agents/vet-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 763 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00763
Opus 5	$0.00005	$0.00381
Sonnet 5	$0.00002	$0.00153
Haiku 4.5	$0.00001	$0.00076

Measured 9d ago against content hash bcf15e80f598, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vet-spec 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 9d 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.

.agents/commands/vet-spec.md · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Your task is to evaluate whether a specification is ready to be implemented: aligned with the project, feasible given the codebase, free of structural risk, complete enough to be implemented without divergent interpretation, with appropriate quality-attribute tradeoffs.

Task

Use the review-spec Agent Skill to drive every phase: resolve the task reference, build project context, read the specification thoroughly, evaluate it against the six dimensions (alignment, feasibility, risks, completeness, tradeoffs, recommendations), then compose the review.
The command receives two arguments:
1. Task name - a brief description of the feature OR a GitHub issue reference (https://github.com/owner/repo/issues/123, owner/repo#123, #123).
2. Spec path - the path to the specification markdown file.
If the task argument is a GitHub issue reference, the skill's Phase 1 fetches context with gh issue view <ref> --json title,body and uses the issue title as the task name and the body as additional context. If the argument is plain text, the skill treats it as the task name verbatim.
Read the spec file in its entirety before evaluating - it is the primary subject of this review.
Discover project context by searching the conventional locations - project context files (AGENTS.md, CLAUDE.md, GEMINI.md, CONTRIBUTING.md, README.md), architecture documentation, ADR sets, build manifests, and schema files. Do not assume specific filenames or paths; the skill's discovery rules apply.

Skill Enforcement

MANDATORY: Apply the review-spec Agent Skill verbatim.

The skill is the single source of truth for how to evaluate the spec, classify findings, and structure the report. The project's context files are the source of truth for what the architecture, layering, naming conventions, and review standards are. Consult each at the moment the skill calls for it.

Process:

Load the review-spec Agent Skill before reading the specification.
Walk through every phase in order. Do not skip, merge, or abbreviate any phase. Each gate prevents a documented failure mode (ungrounded reviews, missed conventions, ambiguity blindness, severity inflation).
If the skill is unavailable in this environment, stop and report the failure. Do not improvise a replacement protocol.
Write the final review to .reviews/Review-spec-{slug}.md per the skill's output rules. Print the path of the file written.

Read the full file on GitHub · 37 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.

9d ago First seen · 37 lines · 9 tokens per session scan A bcf15e80f598

Subscribe to this mod's changes

vet-spec is a command published in the GitHub repository sergeyklay/.agents (5 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 763 once invoked, about $0.0000 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-31.

Planning agent-skills agentic-workflow agents claude-code-skills claude-skills codex-skill

vet-spec

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Task

Skill Enforcement

What this file has done since we first saw it

Other commands, from other repositories

psql-query

ship

test-feature

speckit.polish

review

debug