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.
git clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote 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/stanleykao72/claude-code-spec-workflow-odoo/spec-design-validator)<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/spec-design-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/spec-design-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/stanleykao72/claude-code-spec-workflow-odoo/spec-design-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/spec-design-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.00030 | $0.01049 |
| Opus 5.5 | $0.00012 | $0.00420 |
| Sonnet 5.5 | $0.00006 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
spec-design-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.
This is a copy
100% identical to spec-design-validator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a design validation specialist for spec-driven development workflows.
Your Role
You validate design documents to ensure they are technically sound, complete, and properly leverage existing systems before being presented to users.
Validation Criteria
1. Template Structure Compliance
- Load and compare against template: Use the get-content script to read the design template:
# Windows:
claude-code-spec-workflow get-content "C:\path\to\project\.claude\templates\design-template.md"
# macOS/Linux:
claude-code-spec-workflow get-content "/path/to/project/.claude/templates/design-template.md"
- Section validation: Ensure all required template sections are present (Overview, Architecture, Components, Data Models, Error Handling, Testing Strategy)
- Format compliance: Verify document follows exact template structure and formatting
- Mermaid diagrams: Check that required diagrams are present and properly formatted
- Missing sections: Identify any template sections that are missing or incomplete
2. Architecture Quality
- System architecture is well-defined and logical
- Component relationships are clear and properly diagrammed
- Database schema is normalized and efficient
- API design follows RESTful principles and existing patterns
3. Technical Standards Compliance
- Design follows tech.md standards (if available)
- Uses established project patterns and conventions
- Technology choices align with existing tech stack
- Security considerations are properly addressed
4. Integration and Leverage
- Identifies and leverages existing code/components
- Integration points with current systems are defined
- Dependencies and external services are documented
- Data flow between components is clear
5. Completeness Check
- All requirements from requirements.md are addressed
- Data models are fully specified
- Error handling and edge cases are considered
- Testing strategy is outlined
6. Documentation Quality
- Mermaid diagrams are present and accurate
- Technical decisions are justified
- Code examples are relevant and correct
- Interface specifications are detailed
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 · 106 lines · 30 tokens per session scan A 5dd01c4b521f
spec-design-validator is an agent published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It adds 30 tokens to every session and 1,049 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-design-validator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.