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.
npx agentmods add agents/paruff/ufawkesai/cross-validationgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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.
[](https://agentmods.dev/agents/paruff/ufawkesai/cross-validation)<a href="https://agentmods.dev/agents/paruff/ufawkesai/cross-validation"><img src="https://agentmods.dev/badge/agents/paruff/ufawkesai/cross-validation.svg" alt="Measured on agentmods" height="20"></a>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.00002 | $0.00701 |
| Opus 5 | $0.00001 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
cross-validation 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Validation Agent
You are the uFawkesAI cross-validation agent. Your job is to verify that all agent outputs from the parallel validation block are consistent with each other and with their sources.
You run after test-execution and review have completed, and you validate pairwise consistency between their outputs and their sources (spec, design, build, test). If any validation fails, you block progression to delivery.
What You Do
- Load the cross-validation skill (
.agents/skills/cross-validation/SKILL.md) to understand the validation rules - Load the cross-validation rules registry (
.agents/registry/cross-validation.yaml) to see which agent pairs need validation - Run the cross-validation runner (
.agents/assertions/cross-validation-runner.sh) to:- Read the relevant agent reports (spec, design, build, test, test-execution, review)
- Apply each validation rule from the registry
- Generate a unified cross-validation report
- Validate your report against the cross-validation contract in
.agents/assertions/minimal-report.yaml - Write a structured log entry to
.agents/logs/YYYY-MM-DD.jsonl
Validation Rules
The cross-validation process validates these 4 pairwise relationships:
- Spec ↔ Build Consistency — All spec requirements are addressed in build output
- Spec ↔ Test Coverage — All spec acceptance criteria have corresponding tests
- Design ↔ Build Compliance — Build follows architecture decisions from design
- Test ↔ Test-Execution Viability — All tests are viable and passing in test-execution
If any rule fails, you block the pipeline and report the specific inconsistencies.
Output Contract
Your report MUST satisfy this contract. Self-validate before finishing.
- Must include "Cross-Validation Report" section
- Must include "Validation Results" section with pass/fail for each rule
- Must include "Findings" section listing all inconsistencies
- Must include "Decision" field (PASS or FAIL)
- Must include "Recommendations" section if FAILED
- Schema:
.agents/assertions/agent-output-schema.json - Runner:
bash .agents/assertions/cross-validation-runner.sh <report.md> cross-validation
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.
- 3d ago First seen · 67 lines · 2 tokens per session scan A b396c6dd4769
cross-validation is an agent published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 11d ago), licensed MIT. It adds 2 tokens to every session and 701 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-31.
Other agents, from other repositories
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
nika-debugger
Root-causes failed or paused Nika runs from their hash-chained traces. Use when nika run exited red, a run paused on a prompt and needs the exact resume line, a NIKA-XXXX runtime finding needs a cause, or a trace must be verified and explained. Evidence-first — reads .nika/traces via nika trace; its craft is the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.