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/_plan-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/_plan-validator)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_plan-validator"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_plan-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.00026 | $0.01062 |
| Opus 5 | $0.00013 | $0.00531 |
| Sonnet 5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
PlanValidator 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Evaluate plan.md against Plan → Tasks phase-boundary criteria.
Inputs
Plan path and spec path.
Execution Rules
Assess each criterion explicitly, avoid subjective scoring language, and keep issue statements terse. Run declared-dependency installability checks for real (read-only verdict on the result); never simulate a pass.
Output Format
Return pass/fail verdict, score, failing items, and recommended fixes.
- Run
node scripts/parse-requirement-ownership.mjs "SpecPath"from the repository root. A parser failure makes P1 Requirement Coverage FAIL. Use its orderedp1RequirementIdsas the live P1 set. Accept suppliedP1RequirementIdsonly when it is an exact ordered match; otherwise discard it and use the live set. An empty supplied array is valid only when the successful live parser also returns an empty array. Never infer priority from proximity or treat parser ambiguity as no P1 requirements. RunevaluatePlanGatefromscripts/phase-gates.mjswith the plan bytes and this live P1 set; its verdict is canonical for deterministic criteria below. - Parse the
## Requirement Coverage Mapfromplan.mdinto rows of{reqID, components, filePaths, functions}. - Parse the
## Architecture Decisionstable intoAD-###IDs and their referenced requirement/component scope. - Parse
## Testing Strategy(or legacy## QC Tooling) and## Source Codesections for declared dependencies and package manifests. - Evaluate each criterion as PASS or FAIL (quote specific issue if failing):
P1 Requirement Coverage
- Every P1 requirement ID from
spec.mdappears as a row in the Requirement Coverage Map - Every P1 coverage-map row has a non-empty
File Path(s)column - Every P1 coverage-map row has a non-empty
Function(s)/Symbol(s)column - No P1 coverage-map row has a placeholder (
[REPLACE: ...],TBD,—as the sole value) inFile Path(s)orFunction(s)/Symbol(s)
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.
- 4d ago First seen · 74 lines · 26 tokens per session scan A d8595a021f82
PlanValidator is an agent published in the GitHub repository attilaszasz/sdd-pilot (95 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,062 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
performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
a11y-architect
Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI components, establishing design systems, or auditing code for inclusive user experiences.
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
opensource-forker
Fork any project for open-sourcing. Copies files, strips secrets and credentials (20+ patterns), replaces internal references with placeholders, generates .env.example, and cleans git history. First stage of the opensource-pipeline skill.