validate

A command for managing the validation stage of a planned software change, including acceptance checks, regression checks, browser evidence, and observability checks.

In plain words
What is it for?
Use it to inspect or update validation status and attach requested evidence to the session’s evidence folder.
Why use it?
It keeps validation details in the current session’s runbook so readiness and blockers are recorded in one place.

Command

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/done-0/openarche/validate
Clone the repo
git clone --depth 1 https://github.com/Done-0/openarche
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 273 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.00008 $0.00273
Opus 5 $0.00004 $0.00137
Sonnet 5 $0.00002 $0.00055
Haiku 4.5 $0.00001 $0.00027

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

Security

Grade A, and why

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

commands/validate.md · 34 lines

What it actually says

Use this command to inspect or update the validation stage for the current harness session.

Required behavior:

  1. Prefer the current session state in .openarche/sessions/<task-id>/state.json. Only create a separate note when the user explicitly asks for one.
  2. Read the current runbook.validation section and keep its structure stable.
  3. Use runbook.validation as the source of truth for:
    • acceptance checks
    • regression checks
    • browser validation state
    • observability validation state
    • blockers
    • readiness
  4. If the user is attaching validation evidence, update runbook.validation and store any file evidence under .openarche/sessions/<task-id>/evidence/ instead of inventing a parallel format.
  5. Keep validation conclusions aligned with current product rules:
    • acceptance checks must pass
    • regression checks must pass
    • browser evidence is required when browser validation is enabled
    • observability evidence is required when observability checks are present

When presenting the validation work, organize it into:

  • acceptance checks
  • regression checks
  • browser journeys and required browser evidence
  • observability evidence
  • blockers that still keep validation open
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 · 34 lines · 8 tokens per session scan A 0ce8d313699b

Subscribe to this mod's changes

validate is a command published in the GitHub repository Done-0/openarche (12 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 273 once invoked, about $0.0000 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.