speckit: Skill for Claude Code

.claude/skills/spec-validation/SKILL.md

spec-validation is a skill for Claude Code from jmanhype/speckit. It costs 38 tokens per session (965 once invoked), scanned A, original, MIT.

A specification-checking guide that evaluates whether requirements are technology-independent, complete, and easy to test.

In plain words
What is it for?
Use it when reviewing requirements, checking specifications, or deciding whether a specification is ready for technical planning.
Why use it?
It helps expose vague requirements and implementation details that could make a specification hard to review or verify.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is jmanhype/speckit's own configuration. It tells Claude Code how to work on speckit 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 speckit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jmanhype/speckit. 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/jmanhype/speckit/main/.claude/skills/spec-validation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jmanhype/speckit

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 spec-validation

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmanhype/speckit/spec-validation/github.svg)](https://agentmods.dev/skills/jmanhype/speckit/spec-validation)
Your own site
<a href="https://agentmods.dev/skills/jmanhype/speckit/spec-validation"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/spec-validation/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 spec-validation

Your own site · 80×15
<a href="https://agentmods.dev/skills/jmanhype/speckit/spec-validation"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/spec-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 965 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00965
Opus 5.5 $0.00015 $0.00386
Sonnet 5.5 $0.00008 $0.00193
Haiku 4.5 $0.00004 $0.00097

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

Security

Grade A, and why

spec-validation 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/spec-validation/SKILL.md · 164 lines

How it starts

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

Spec Validation Skill

You are validating specifications in a Spec Kit workflow. This skill ensures specifications meet quality standards before proceeding to technical planning.

Validation Criteria

1. Technology Agnosticism

Specifications must describe WHAT and WHY, not HOW. Flag any references to:

Frameworks & Libraries

  • ❌ React, Vue, Angular, Django, FastAPI, Express
  • ❌ Redux, MobX, Zustand (state management)
  • ❌ Tailwind, Bootstrap, Material UI (styling)

Languages & Syntax

  • ❌ async/await, promises, callbacks
  • ❌ decorators, hooks, mixins
  • ❌ specific type systems

Databases & Storage

  • ❌ PostgreSQL, MongoDB, Redis, S3
  • ❌ SQL queries, NoSQL patterns
  • ❌ Specific ORM syntax

Infrastructure

  • ❌ Docker, Kubernetes, AWS, GCP
  • ❌ Specific API protocols (REST, GraphQL, gRPC)
  • ❌ Deployment patterns

Good Example:

Users can view their order history sorted by date.

Bad Example:

Use React Query to fetch orders from the REST API and display in a Tailwind-styled table.

2. Testability

Every requirement must be verifiable. Flag:

Vague Requirements

  • ❌ "System should be fast"
  • ❌ "Good user experience"
  • ❌ "Intuitive interface"
  • ❌ "Improve performance"

Subjective Criteria

  • ❌ "Easy to use"
  • ❌ "Modern design"
  • ❌ "Scalable architecture"

Good Examples:

- Page loads in under 2 seconds on 3G connection
- Form validates email format before submission
- Users receive confirmation within 24 hours
- System handles 1000 concurrent users

3. Completeness

Check for:

Missing Scenarios

  • Happy path (main flow)
  • Error cases (what can go wrong)
  • Edge cases (boundary conditions)
  • Empty/null states

Undefined Terms

  • Acronyms without definitions
  • Domain-specific terms
  • Ambiguous references ("the system", "it")

Missing Acceptance Criteria

  • Success conditions
  • Error conditions
  • Performance requirements
  • Security requirements

4. Consistency

Verify:

  • No contradicting requirements
  • Consistent terminology
  • Aligned with constitution (if exists)
  • No duplicate requirements

Read the full file on GitHub · 164 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 First seen · 164 lines · 38 tokens per session scan A 2867068bde3f

Subscribe to this mod's changes

spec-validation is a skill published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 965 once invoked, about $0.0002 per session on Opus 5.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-09-01.