SharpPad: Command for Claude Code

.claude/commands/kiro/validate-design.md

validate-design is a command for Claude Code from gaoconggit/SharpPad. It costs 7 tokens per session (1,333 once invoked), scanned A, a copy of validate-design, MIT.

An interactive reviewer for technical design documents in Kiro projects. It checks whether a proposed design fits the existing architecture and project guidance.

In plain words
What is it for?
Use it to review a feature's requirements, design, architecture documents, technology guidance, and custom steering files.
Why use it?
It finds critical design problems before implementation and provides a go-or-no-go decision with reasons.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

This is gaoconggit/SharpPad's own configuration. It tells Claude Code how to work on SharpPad itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SharpPad configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gaoconggit/SharpPad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gaoconggit/SharpPad/main/.claude/commands/kiro/validate-design.md
Clone the repo
git clone --depth 1 https://github.com/gaoconggit/SharpPad

Made for: Claude Code.

Wrote 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.

agentmods badge for validate-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/gaoconggit/sharppad/validate-design/github.svg)](https://agentmods.dev/commands/gaoconggit/sharppad/validate-design)
Your own site
<a href="https://agentmods.dev/commands/gaoconggit/sharppad/validate-design"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/validate-design/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.

agentmods 80×15 button for validate-design

Your own site · 80×15
<a href="https://agentmods.dev/commands/gaoconggit/sharppad/validate-design"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/validate-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.01333
Opus 5.5 $0.00003 $0.00533
Sonnet 5.5 $0.00001 $0.00267
Haiku 4.5 $0.00001 $0.00133

Measured 13d ago against content hash 3fca02abb7cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-design 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 13d 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.

Origin

This is a copy

95% identical to validate-design — 2 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.

.claude/commands/kiro/validate-design.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Technical Design Validation

Interactive design quality review for feature: $1

Context Loading

Prerequisites Validation

  • Design document must exist: .kiro/specs/$1/design.md
  • If not exist, stop with message: "Run /kiro:spec-design $1 first to generate design document"

Review Context

  • Spec metadata: @.kiro/specs/$1/spec.json
  • Requirements document: @.kiro/specs/$1/requirements.md
  • Design document: @.kiro/specs/$1/design.md
  • Core steering documents:
    • Architecture: @.kiro/steering/structure.md
    • Technology: @.kiro/steering/tech.md
    • Product context: @.kiro/steering/product.md
  • Custom steering: All additional .md files in .kiro/steering/ directory

Task: Interactive Design Quality Review

Review Methodology

Focus: Critical issues only - limit to 3 most important concerns Format: Interactive dialogue with immediate feedback and improvement suggestions Outcome: GO/NO-GO decision with clear rationale

Core Review Criteria

1. Existing Architecture Alignment (Critical)

Evaluation Points:

  • Integration with existing system boundaries and layers
  • Consistency with established architectural patterns
  • Proper dependency direction and coupling management
  • Alignment with current module organization and responsibilities

Review Questions:

  • Does this design respect existing architectural boundaries?
  • Are new components properly integrated with existing systems?
  • Does the design follow established patterns and conventions?
2. Design Consistency & Standards

Evaluation Points:

  • Adherence to project naming conventions and code standards
  • Consistent error handling and logging strategies
  • Uniform approach to configuration and dependency management
  • Alignment with established data modeling patterns

Review Questions:

  • Is the design consistent with existing code standards?
  • Are error handling and configuration approaches unified?
  • Does naming and structure follow project conventions?
3. Extensibility & Maintainability

Evaluation Points:

  • Design flexibility for future requirements changes
  • Clear separation of concerns and single responsibility principle
  • Testability and debugging considerations
  • Documentation and code clarity requirements

Read the full file on GitHub · 180 lines

Changes

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.

  1. 13d ago First seen · 180 lines · 7 tokens per session scan A 3fca02abb7cd

Subscribe to this mod's changes

validate-design is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 1,333 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to validate-design, differing in 2 lines, and is treated as a copy.