validation_system

A draft requirements document for a validation-agent system: software that checks whether work completed by other agents meets defined requirements. It covers workflow states, stored data, APIs, settings, service targets, security, memory, and diagnosis.

In plain words
What is it for?
Use it as a reference when designing the validation workflow, database and API contracts, configuration, events, reliability targets, security controls, memory handling, and links to diagnosis services.
Why use it?
It gives the validation system explicit rules for moving tasks through review and for recording whether validation passed or failed.

Agent

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/kivo360/omoios/validation_system
Clone the repo
git clone --depth 1 https://github.com/kivo360/OmoiOS
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 2,205 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.00000 $0.02205
Opus 5 $0.00000 $0.01103
Sonnet 5 $0.00000 $0.00441
Haiku 4.5 $0.00000 $0.00220

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

Security

Grade A, and why

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

docs/requirements/agents/validation_system.md · 253 lines

How it starts

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

Validation System Requirements

Created: 2025-11-20 Status: Draft Purpose: Define normative requirements for the Validation Agent System, covering state machine, data model, API, configuration, SLOs, security, memory, and diagnosis integration. Related: docs/requirements/workflows/multi_agent_orchestration.md, docs/design/agents/validation_agent_design.md, docs/requirements/services/memory_system.md, docs/requirements/services/diagnosis_system.md


Document Overview

This document defines normative requirements for the Validation Agent System, including state machine extensions, database artifacts, API contracts, configuration, events, and Pydantic reference models.

Parent Document: Multi-Agent Orchestration Requirements


1. State Machine Extensions

REQ-VAL-SM-001: Validation States

THE SYSTEM SHALL support the following validation states and transitions:

stateDiagram-v2
    [*] --> pending
    pending --> assigned : Task Created
    assigned --> in_progress : Agent Assigned
    in_progress --> under_review : Agent Claims Done
    under_review --> validation_in_progress : Validator Spawned
    validation_in_progress --> done : Validation Passes
    validation_in_progress --> needs_work : Validation Failed
    needs_work --> in_progress : Agent Resumes (same session)
    in_progress --> failed : Agent Gives Up
    done --> [*]
    failed --> [*]
REQ-VAL-SM-002: Guards
  • Transition to under_review requires agent to publish completion signal and commit SHA (if applicable).
  • Transition to validation_in_progress requires successful validator spawn.
  • Transition to done requires validation_passed==true.
  • Transition to needs_work requires validation_passed==false and feedback present.

2. Data Model Requirements

2.1 Task Model Extensions

REQ-VAL-DM-001

Add the following fields to Task:

  • validation_enabled: bool (default: false)
  • validation_iteration: int (default: 0)
  • last_validation_feedback: str | null
  • review_done: bool (default: false)

Read the full file on GitHub · 253 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 · 253 lines · 0 tokens per session scan A 1d52fdb9a39a

Subscribe to this mod's changes

validation_system is an agent published in the GitHub repository kivo360/OmoiOS (75 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,205 tokens. 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.