Borrowing it
Nothing to install: this file belongs to j5ik2o/okite-ai. 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/j5ik2o/okite-ai/main/.claude/commands/kiro/validate-impl.mdgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/validate-impl)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/validate-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/validate-impl/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/j5ik2o/okite-ai/validate-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/validate-impl.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.01237 |
| Opus 5.5 | $0.00000 | $0.00495 |
| Sonnet 5.5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
validate-impl 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- validate-impl — 100% identical, 0 lines differ
- kiro-validate-impl — 89% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Validation
<background_information>
- Mission: Verify that implementation aligns with approved requirements, design, and tasks
- Success Criteria:
- All specified tasks marked as completed
- Tests exist and pass for implemented functionality
- Requirements traceability confirmed (EARS requirements covered)
- Design structure reflected in implementation
- No regressions in existing functionality </background_information>
Execution Steps
1. Detect Validation Target
If no arguments provided ($1 empty):
- Parse conversation history for
/kiro:spec-impl <feature> [tasks]commands - Extract feature names and task numbers from each execution
- Aggregate all implemented tasks by feature
- Report detected implementations (e.g., "user-auth: 1.1, 1.2, 1.3")
- If no history found, scan
.kiro/specs/for features with completed tasks[x]
If feature provided ($1 present, $2 empty):
- Use specified feature
- Detect all completed tasks
[x]in.kiro/specs/$1/tasks.md
If both feature and tasks provided ($1 and $2 present):
- Validate specified feature and tasks only (e.g.,
user-auth 1.1,1.2)
2. Load Context
For each detected feature:
- Read
.kiro/specs/<feature>/spec.jsonfor metadata - Read
.kiro/specs/<feature>/requirements.mdfor requirements - Read
.kiro/specs/<feature>/design.mdfor design structure - Read
.kiro/specs/<feature>/tasks.mdfor task list - Load ALL steering context: Read entire
.kiro/steering/directory including:- Default files:
structure.md,tech.md,product.md - All custom steering files (regardless of mode settings)
- Default files:
3. Execute Validation
For each task, verify:
Task Completion Check
- Checkbox is
[x]in tasks.md - If not completed, flag as "Task not marked complete"
Test Coverage Check
- Tests exist for task-related functionality
- Tests pass (no failures or errors)
- Use Bash to run test commands (e.g.,
npm test,pytest) - If tests fail or don't exist, flag as "Test coverage issue"
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 · 139 lines · 0 tokens per session scan A 006ea72c7a84
validate-impl is a command published in the GitHub repository j5ik2o/okite-ai (80 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,237 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-09-01.
Other commands, from other repositories
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
auditar-refactor
Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
claude-loop
Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.