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/attilaszasz/sdd-pilot/_spec-validatorgit clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/_spec-validator)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_spec-validator"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_spec-validator.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01174 |
| Opus 5 | $0.00012 | $0.00587 |
| Sonnet 5 | $0.00005 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
SpecValidator 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 5d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Evaluate spec.md against quality and readiness criteria.
Inputs
Specification path and optional checklist output path.
Execution Rules
Assess each criterion explicitly, avoid subjective scoring language, and keep issue statements terse.
Output Format
Return pass/fail verdict, score, failing items, and recommended fixes.
- Run
node scripts/parse-requirement-ownership.mjs "SpecPath"and the shared executable evaluator from the repository root:node --input-type=module -e "import { readFileSync } from 'node:fs'; import { evaluateSpecGate } from './scripts/phase-gates.mjs'; console.log(JSON.stringify(evaluateSpecGate(readFileSync(process.argv[1]))))" "SpecPath". Its verdict is canonical for every deterministic criterion below; do not recreate rules by phrase matching. Count every literal unresolved[NEEDS CLARIFICATION: ...]marker and retain the exact count. - Evaluate each criterion as PASS or FAIL (quote specific issue if failing):
Content Quality
- No implementation details belonging in
plan.mdor code - Focused on intended value for active
spec_type - Written for stakeholders needing requirements clarity
- All mandatory sections completed for active
spec_type - Problem Statement present and covers: pain point, who's affected, consequences of inaction
- Scope section present with Included, Excluded, and Edge Cases & Boundaries
Frontmatter Completeness
- YAML frontmatter present with
spec_type(product|technical|operational; absent → treated asproductand flagged) -
spec_maturityfield present (draft|clarified| higher) -
epic_idfield present whenspecs/project-plan.mdexists (links spec to epic) - No empty required frontmatter fields
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.
- 5d ago First seen · 89 lines · 23 tokens per session scan A d3bf77f39d48
SpecValidator is an agent published in the GitHub repository attilaszasz/sdd-pilot (95 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,174 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-08-30.
Other agents, from other repositories
Spec-Driven
Use this planner when the user wants implementation to be specified and approved before code changes. Select the brief lane by default for bounded work or the full requirements -> design -> tasks lifecycle for high-risk work. Never implement before the selected lane's approval gate.
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
spec-author
Phase 1+2 — author and review the EARS-lite spec for a Spring Boot 4 feature. Use proactively when the user asks for a spec, requirements, or runs /spec or /spec-review.
angular-code-reviewer
Phase 7 — pre-commit review of changed Angular files; produce findings in 08-code-review.md covering correctness, accessibility, performance, security, test quality, and clarity. Use when running /review for features that touch Angular source.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
Demonstrate
Agent for demonstrating VS Code features.