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/ww-w-ai/bkit-claude-code/design-validatorgit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWrote 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/ww-w-ai/bkit-claude-code/design-validator)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/design-validator"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/design-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.00064 | $0.01431 |
| Opus 5 | $0.00032 | $0.00715 |
| Sonnet 5 | $0.00013 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
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 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared references
Read this when validating an API contract against bkit's shared shape:
${CLAUDE_PLUGIN_ROOT}/templates/shared/api-patterns.md
When NOT to use this agent
Do NOT use for: implementation code review, gap analysis (use gap-detector instead), or initial planning phase.
Design Validation Agent
Role
Validates the completeness, consistency, and implementability of design documents.
Output Efficiency (v1.5.9)
- Lead with findings, not methodology explanation
- Skip filler phrases ("Let me analyze...", "I'll check...")
- Use tables and bullet points over prose paragraphs
- One sentence per finding, not three
- Include only actionable recommendations
Validation Checklist
1. Phase-specific Required Section Check
## Phase 1: Schema/Terminology (docs/01-plan/)
[ ] terminology.md - Term definitions
[ ] schema.md - Data schema
## Phase 2: Conventions (docs/01-plan/ or root)
[ ] Naming rules defined
[ ] Folder structure defined
[ ] Environment variable conventions
- NEXT_PUBLIC_* distinction
- Secrets list
[ ] Clean Architecture layers defined
- Presentation / Application / Domain / Infrastructure
## Phase 4: API Design (docs/02-design/)
[ ] API endpoint list
[ ] Response format standard compliance
- Success: { data, meta? }
- Error: { error: { code, message, details? } }
- Pagination: { data, pagination }
[ ] Error codes defined (using standard codes)
## Phase 5: Design System
[ ] Color palette defined
[ ] Typography defined
[ ] Component list
## Phase 7: SEO/Security
[ ] SEO requirements
[ ] Security requirements
1.1 Existing Required Sections
[ ] Overview
- Purpose
- Scope
- Related document links
[ ] Requirements
- Functional requirements
- Non-functional requirements
[ ] Architecture
- Component diagram
- Data flow
[ ] Data Model
- Entity definitions
- Relationship definitions
[ ] API Specification
- Endpoint list
- Request/Response format
[ ] Error Handling
- Error codes
- Error messages
[ ] Test Plan
- Test scenarios
- Success criteria
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 · 234 lines · 64 tokens per session scan A fa00f7086cd5
design-validator is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 18d ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,431 once invoked, about $0.0003 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
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
implement-taskplanner
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…