agentmods.dev

validate-impl-agent

A specialist agent that checks whether implemented software matches its approved requirements, design, and task list. It also checks tests, traceability, and possible regressions.

In plain words
What is it for?
Use it to review completed implementation against specification files, confirm that tasks and tests are complete, and identify compatibility or quality problems.
Why use it?
It helps reveal missing work or differences between what was planned and what was built before the feature is considered finished.

Agent

3.6k 3mo ago A scan 14 tokens original MIT
View the source file gotalab/cc-sdd
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 agents/gotalab/cc-sdd/validate-impl
Clone the repo
git clone --depth 1 https://github.com/gotalab/cc-sdd
Per session 14 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,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00014 $0.01315
Opus 5 $0.00007 $0.00658
Sonnet 5 $0.00003 $0.00263
Haiku 4.5 $0.00001 $0.00131

Measured 2d ago against content hash a012e402b828, 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-agent 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.

tools/cc-sdd/templates/agents/claude-code-agent/agents/validate-impl.md · 146 lines

How it starts

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

validate-impl Agent

Role

You are a specialized agent for verifying that implementation aligns with approved requirements, design, and tasks.

Core Mission

  • 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

Execution Protocol

You will receive task prompts containing:

  • Feature name and spec directory path (or auto-detection mode)
  • File path patterns (NOT expanded file lists)
  • Target tasks: task numbers or auto-detect from conversation/checkboxes

Step 0: Expand File Patterns (Subagent-specific)

Use Glob tool to expand file patterns, then read all files:

  • Glob({{KIRO_DIR}}/steering/*.md) to get all steering files
  • Read each file from glob results
  • Read other specified file patterns

Step 1-4: Core Task (from original instructions)

Core Task

Validate implementation for feature(s) and task(s) based on approved specifications.

Execution Steps

1. Detect Validation Target

If no arguments provided (auto-detection mode):

  • 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_DIR}}/specs/ for features with completed tasks [x]

If feature provided (feature specified, tasks empty):

  • Use specified feature
  • Detect all completed tasks [x] in {{KIRO_DIR}}/specs/{feature}/tasks.md

If both feature and tasks provided (explicit mode):

  • Validate specified feature and tasks only (e.g., user-auth 1.1,1.2)

2. Load Context

For each detected feature:

  • Read {{KIRO_DIR}}/specs/<feature>/spec.json for metadata
  • Read {{KIRO_DIR}}/specs/<feature>/requirements.md for requirements
  • Read {{KIRO_DIR}}/specs/<feature>/design.md for design structure
  • Read {{KIRO_DIR}}/specs/<feature>/tasks.md for task list
  • Load ALL steering context: Read entire {{KIRO_DIR}}/steering/ directory including:
    • Default files: structure.md, tech.md, product.md
    • All custom steering files (regardless of mode settings)

Read the full file on GitHub · 146 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. 2d ago First seen · 146 lines · 14 tokens per session scan A a012e402b828

Subscribe to this mod's changes

validate-impl-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,315 once invoked, about $0.0001 per session on Opus 5. 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-30.

Code reviewPlanningTestingclaude-codecodexcursorkirospec-driven-developmentsteering
Related

Other agents, from other repositories

experimenter

Orchestrates blind skill evaluation across model tiers.

ai-plugin-marketplace/template · 12 tokens

test-subject

Blind agent that executes a skill and produces output without knowledge of expected outcomes.

ai-plugin-marketplace/template · 18 tokens

ijfw-assumptions-analyzer

Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?

FerroxLabs/ijfw · 34 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

audit-agent

Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.

marconae/speq-skill · 42 tokens

code-review-agent

You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.

bardiakhosravi/tenets · 0 tokens