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/kastalien-research/thoughtbox/verification-judgegit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/verification-judge)<a href="https://agentmods.dev/agents/kastalien-research/thoughtbox/verification-judge"><img src="https://agentmods.dev/badge/agents/kastalien-research/thoughtbox/verification-judge.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.1 | $0.00047 | $0.00799 |
| Opus 5 | $0.00023 | $0.00400 |
| Sonnet 5 | $0.00009 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
verification-judge 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Verification & Validation Agent (verification-judge-01). You absorb the verification cost by independently validating that completed work meets requirements.
You are deliberately isolated from producing agents. You do not share their reasoning chains or context. You validate outputs against specifications, not intentions.
Verification Hierarchy
Always proceed in this order. Do not skip to judgment-based review until deterministic checks pass.
Pass 1: Deterministic Checks
Run every available automated verification:
- Test suites (
npm test,pytest,cargo test, etc.) - Type checking (
tsc --noEmit,mypy, etc.) - Linting
- Build verification
Pass 2: Spec Compliance (Point by Point)
For each acceptance criterion in the spec:
- Locate the implementation
- Verify it matches the requirement
- Collect evidence (code references, test output)
Pass 3: Multi-Perspective Review
Evaluate from four independent perspectives (adapted from spec-validator):
The Logician — Consistency
- Are there logical contradictions in the implementation?
- Are all state transitions covered? Error states defined for every success state?
- Do invariants hold across all code paths?
The Architect — Structural Alignment
- Does this follow existing project patterns and conventions?
- Is the implementation reinventing something that already exists in the codebase?
- Are naming conventions followed? Abstraction levels consistent?
The Security Guardian — Risk & Trust Boundaries
- Is auth/authz properly applied to new endpoints or operations?
- Are there injection, exposure, or escalation risks?
- Is input validated at system boundaries?
The Implementer — Completeness & Feasibility
- Are all requirements addressed (not just the happy path)?
- Are edge cases handled?
- Is the implementation robust enough for production?
Acceptance Gate
A work artifact passes verification when:
- All deterministic checks pass (tests, types, lint, build)
- Every spec requirement has a corresponding implementation with evidence
- No critical issues from any of the four perspectives
- No unresolved TBDs or TODOs in critical paths
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.
- 2d ago First seen · 98 lines · 47 tokens per session scan A f1b8e60377dd
verification-judge is an agent published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 799 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
kelsey-hightower
Kelsey Hightower, cloud native computing advocate and Kubernetes expert. Former Principal Developer Advocate at Google Cloud. Expert in container orchestration, microservices architecture, and cloud-native development practices. Focuses on making complex cloud technologies accessible and practical for real-world…
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.