validate-impl

Install

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.

agentmods

npx agentmods add commands/j5ik2o/event-store-adapter-js/validate-impl

Clone the repo

git clone --depth 1 https://github.com/j5ik2o/event-store-adapter-js

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/validate-impl.svg)](https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/validate-impl)

Your own site

<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/validate-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/validate-impl.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 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,237 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 89% 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01237
Opus 5	$0.00000	$0.00619
Sonnet 5	$0.00000	$0.00247
Haiku 4.5	$0.00000	$0.00124

Measured 2d ago against content hash 006ea72c7a84, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

.claude/commands/kiro/validate-impl.md · 139 lines

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.

description: Validate implementation against requirements, design, and tasks allowed-tools: Bash, Glob, Grep, Read, LS argument-hint: [feature-name] [task-numbers]

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.json for metadata
Read .kiro/specs/<feature>/requirements.md for requirements
Read .kiro/specs/<feature>/design.md for design structure
Read .kiro/specs/<feature>/tasks.md for 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)

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"

Read the full file on GitHub · 139 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.

2d ago First seen · 139 lines · 0 tokens per session scan A 006ea72c7a84

Subscribe to this mod's changes

validate-impl is a command published in the GitHub repository j5ik2o/event-store-adapter-js (24 stars, last pushed 3d ago), licensed Apache-2.0. 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. It is 89% identical to kiro-validate-impl, differing in 18 lines, and is treated as a copy.

cqrs ddd dynamodb event-sourcing