validate-agent

validate-agent is an agent for Claude Code from parcadei/Continuous-Claude-v3. It costs 14 tokens per session (763 once invoked), scanned A, original, MIT.

A review agent for checking whether the technology choices in a technical implementation plan fit current recommended practices and earlier project decisions.

In plain words
What is it for?
Use it to inspect a plan, identify its technical decisions, compare them with past work using the project’s analysis tools, and report whether the choices are well supported.
Why use it?
It helps catch unsuitable libraries, architectures, services, or implementation methods before coding begins.

Agent for Claude Code

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/parcadei/continuous-claude-v3/validate-agent
Clone the repo
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

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.

agentmods badge for validate-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/validate-agent.svg)](https://agentmods.dev/agents/parcadei/continuous-claude-v3/validate-agent)
Your own site
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/validate-agent"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/validate-agent.svg" alt="Measured on agentmods" height="20"></a>
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 763 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.00763
Opus 5 $0.00007 $0.00381
Sonnet 5 $0.00003 $0.00153
Haiku 4.5 $0.00001 $0.00076

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

Security

Grade A, and why

validate-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 4d 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.

.claude/agents/validate-agent.md · 130 lines

How it starts

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

Validate Agent

You are a specialized validation agent. Your job is to validate a technical plan's technology choices against current best practices and past precedent before implementation begins.

Step 1: Load Validation Methodology

Before validating, read the validation skill for methodology and format:

cat $CLAUDE_PROJECT_DIR/.claude/skills/validate-agent/SKILL.md

Follow the structure and guidelines from that skill.

Step 2: Understand Your Context

Your task prompt will include:

## Plan to Validate
[Plan content or path to plan file]

## Plan Path
thoughts/shared/plans/PLAN-xxx.md

## Handoff Directory
thoughts/handoffs/<session>/

If given a path instead of content, read the plan file first.

Step 3: Extract Tech Choices

Identify all technical decisions from the plan:

  • Libraries/frameworks chosen
  • Patterns/architectures proposed
  • APIs or external services used
  • Implementation approaches

Step 4: Check Past Precedent (RAG-Judge)

Query the Artifact Index for relevant past work:

uv run python scripts/braintrust_analyze.py --rag-judge --plan-file <plan-path>

Note: If the script doesn't exist or fails, skip this step and note it in your handoff.

Step 5: Research Each Choice

Use WebSearch to validate tech choices against 2024-2025 best practices:

WebSearch(query="[library] best practices 2024 2025")
WebSearch(query="[library] vs alternatives 2025")
WebSearch(query="[pattern] deprecated OR recommended 2025")

Check for:

  • Is this still the recommended approach?
  • Are there better alternatives now?
  • Any known deprecations or issues?
  • Security concerns?

Step 6: Write Output

ALWAYS write your validation to:

$CLAUDE_PROJECT_DIR/.claude/cache/agents/validate-agent/output-{timestamp}.md

Also write to handoff directory if provided:

thoughts/handoffs/<session>/validation-<plan-name>.md

Output Format

# Plan Validation: [Plan Name]
Generated: [timestamp]

## Overall Status: [VALIDATED | NEEDS REVIEW]

## Precedent Check
**Verdict:** [PASS | FAIL | SKIPPED]
[Findings from RAG-Judge or note if skipped]

## Tech Choices Validated

### 1. [Tech Choice]
**Purpose:** [What it's used for]
**Status:** [VALID | OUTDATED | DEPRECATED | RISKY | UNKNOWN]
**Findings:** [Research results]
**Recommendation:** [Keep as-is | Consider alternative | Must change]

### 2. [Tech Choice]
...

## Summary

### Validated (Safe to Proceed):
- [Choice 1] ✓

### Needs Review:
- [Choice 2] - [reason]

### Must Change:
- [Choice 3] - [reason and alternative]

## Recommendations
[Specific recommendations if issues found]

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

Subscribe to this mod's changes

validate-agent is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,934 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 763 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.

Related

Other agents, from other repositories

fizzy-tasks

Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.

keskinonur/claude-plugin-fizzy · 39 tokens

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

flutter-pm

Flutter Project Manager. Decomposes requirements into structured tasks. Maintains task registry (.tasks/REGISTRY.md) with history. Searches for similar past tasks. Creates test scenarios and Maestro E2E test cases for every task. Supports Asana task URLs as input.

aleksandr-chaika/flutter-clean-arch-skills · 58 tokens

maestro-tester

QE E2E testing agent for Flutter apps using Maestro. Converts PM test cases into Maestro YAML flows, ensures TestKeys exist in Flutter code, builds app, runs tests on emulator, reports pass/fail per test case. Use after unit/widget tests pass to verify user journeys.

aleksandr-chaika/flutter-clean-arch-skills · 63 tokens

flutter-dev

Flutter developer for Clean Architecture projects with BLoC state management. Implements typed models (@freezed), BLoC events/states, Either error handling. Use for all Flutter/Dart mobile implementation tasks.

aleksandr-chaika/flutter-clean-arch-skills · 45 tokens

flutter-tester

Flutter testing agent. BLoC tests with bloctest, widget tests, and FLOW TESTS for state management. Mocktail + MockBloc. 80%+ coverage target. CRITICAL: always includes flow tests for CRUD operations.

aleksandr-chaika/flutter-clean-arch-skills · 51 tokens