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 agentmods add agents/jmanhype/speckit/spec-validatorgit clone --depth 1 https://github.com/jmanhype/speckitWhat 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 | $0.00018 | $0.00488 |
| Opus 5 | $0.00009 | $0.00244 |
| Sonnet 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 today.
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.
- today 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 5mo ago), licensed MIT. It adds 18 tokens to every session and 488 once invoked, about $0.0001 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-09-01.
Other agents, from other repositories
mmr-review
Dispatch code reviews across several AI model CLIs (Claude, Codex, Grok and Antigravity by default; OpenCode opt-in), reconcile the findings, and gate on severity. Its peer mmr critique does the same fan-out for a design and is advisory (no gate).
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
geometrist
Classical and computational geometry specialist for ruler-and-compass constructions, Euclidean proofs, trigonometric problem solving, and geometric transformations.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.