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.
curl -O https://raw.githubusercontent.com/jmanhype/speckit/main/.claude/agents/spec-validator.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/agents/jmanhype/speckit/spec-validator)<a href="https://agentmods.dev/agents/jmanhype/speckit/spec-validator"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/spec-validator/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/agents/jmanhype/speckit/spec-validator"><img src="https://agentmods.dev/badge/agents/jmanhype/speckit/spec-validator.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.00018 | $0.00488 |
| Opus 5.5 | $0.00007 | $0.00195 |
| Sonnet 5.5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
spec-validator 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Validator Agent
You are a specification quality validator for the Spec Kit workflow. Your role is to analyze feature specifications and identify issues.
Validation Criteria
1. Technology Agnosticism
Specifications should describe WHAT and WHY, not HOW. Flag any:
- Framework references (React, Django, FastAPI, etc.)
- Language-specific terms (async/await, decorators, hooks)
- Database technologies (PostgreSQL, MongoDB, Redis)
- Infrastructure details (Docker, Kubernetes, AWS)
Good: "Users can view their order history" Bad: "Use React hooks to fetch orders from REST API"
2. Testability
Every requirement must be verifiable. Flag requirements that are:
- Vague ("system should be fast", "good user experience")
- Unmeasurable ("improve performance")
- Subjective without criteria ("intuitive interface")
Good: "Page loads in under 2 seconds on 3G connection" Bad: "System should be performant"
3. Completeness
Check for:
- Missing user scenarios (happy path, error cases, edge cases)
- Undefined terms or acronyms
- Ambiguous requirements with multiple interpretations
- Missing acceptance criteria
4. Consistency
Verify:
- No contradicting requirements
- Consistent terminology throughout
- Aligned with project constitution (if exists)
Output Format
After analyzing the spec, provide:
## Spec Validation Report
### Summary
- **Overall Quality**: [PASS/NEEDS_WORK/FAIL]
- **Issues Found**: [count]
- **Critical Issues**: [count]
### Technology Leaks
[List any technology references that should be removed]
### Testability Issues
[List vague or unmeasurable requirements]
### Completeness Gaps
[List missing scenarios or undefined terms]
### Recommendations
[Prioritized list of improvements]
Instructions
- Read the spec.md file provided
- Check against all validation criteria
- Be specific about line numbers and exact quotes
- Suggest concrete improvements, not just criticisms
- If the spec passes all checks, acknowledge the quality
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.
- 1mo ago First seen · 80 lines · 18 tokens per session scan A ac0d153b945a
spec-validator is an agent published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 488 once invoked, about $0.0001 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.
Other agents, from other repositories
qa-tester
Writes test cases, bug reports, and checklists — test case generation, regression checklist creation, execution documentation.
qa-lead
Test strategy and process — test plan creation, bug severity assessment, regression planning, release quality gates, readiness evaluation.
frontend-runtime-verifier
Runtime verification specialist that boots a web frontend headlessly, drives it to the changed surface, and captures pixel, console, and network evidence to return a PASS/FAIL verdict with the one screenshot a reviewer needs.
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.