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 commands/j5ik2o/okite-ai/validate-implgit 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.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.00009 | $0.01237 |
| Opus 5 | $0.00005 | $0.00619 |
| Sonnet 5 | $0.00002 | $0.00247 |
| Haiku 4.5 | $0.00001 | $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 2d 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
89% identical to kiro-validate-impl — 18 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 — 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.
- 2d 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 (81 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,237 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to kiro-validate-impl, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.