Borrowing it
Nothing to install: this file belongs to TouheedCode/claude-dev-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TouheedCode/claude-dev-workflow/master/.claude/commands/validate.mdgit clone --depth 1 https://github.com/TouheedCode/claude-dev-workflowWrote 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/commands/touheedcode/claude-dev-workflow/validate)<a href="https://agentmods.dev/commands/touheedcode/claude-dev-workflow/validate"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/validate/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/commands/touheedcode/claude-dev-workflow/validate"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/validate.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.00000 | $0.01348 |
| Opus 5.5 | $0.00000 | $0.00539 |
| Sonnet 5.5 | $0.00000 | $0.00270 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
validate 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 2mo 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate — Quality Gate
Arguments
$ARGUMENTS— Phase identifier (e.g., "Phase 1", "Phase 3") and optionally the story ID
Instructions
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.
Input: $ARGUMENTS
Step 1: Parse Arguments
Extract:
- Phase number (1–7)
- Story ID — if not provided, read from
.phase-context.json
Step 2: Load Expected Deliverables
Read the plan at docs/plans/PLAN-{story-ID}.md and extract the deliverable checklist for the target phase. Each deliverable should have an exact file path.
Step 3: Run Validation Checks
Execute these checks in order. Record pass/fail for each.
Check 1: File Existence
For each deliverable file path in the plan:
- Verify the file exists at the specified path
- Verify the file is non-empty (> 0 bytes)
- Record:
{passed}/{total} files
Check 2: Build
Run the build to catch compilation and type errors early:
# Frontend phases (1-3)
cd apps/web && npx tsc --noEmit
# Backend phases (4-6)
cd apps/api && npx tsc --noEmit
# Phase 7: Both
npm run typecheck
- Record: clean or error count
Check 3: Tests Pass
Run tests scoped to this phase's files:
| Phase | Command |
|---|---|
| 1 | npx vitest run apps/web/src/components/__tests__/ |
| 2 | (no tests — types and hooks only; verify types compile in Check 2) |
| 3 | npx vitest run apps/web/src/app/ |
| 4 | npx vitest run apps/api/src/modules/{module}/__tests__/{module}.repository.integration.spec.ts |
| 5 | npx vitest run apps/api/src/modules/{module}/__tests__/{module}.service.spec.ts |
| 6 | npx vitest run apps/api/src/modules/{module}/__tests__/{module}.e2e.spec.ts |
| 7 | npm run test (full suite) |
- Record:
{passed}/{total} tests - Note: Phase 4 requires Docker running for Testcontainers. If Docker is unavailable, report as
SKIP(not fail).
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.
- 2mo ago First seen · 164 lines · 0 tokens per session scan A 9469cd096d81
validate is a command published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,348 tokens. 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-31.
Other commands, from other repositories
test
A command for running a project's automated tests, which are checks that software behaves as expected. It detects common project types and chooses a matching test command.
qa
A quality-assurance testing agent that checks whether software meets its stated acceptance requirements. It tests normal use, edge cases, failures, and regressions, then classifies the problems it finds.
verify
A command that runs a project's main quality checks in sequence: build, type checking, linting, tests, security scanning, and Git status checks. Linting checks code style and common mistakes; Git tracks file changes.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.