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.
git clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/orc-impl-verifier)<a href="https://agentmods.dev/agents/qgolem/orc/orc-impl-verifier"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-impl-verifier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/qgolem/orc/orc-impl-verifier"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-impl-verifier.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.04802 |
| Opus 5.5 | $0.00013 | $0.01921 |
| Sonnet 5.5 | $0.00007 | $0.00960 |
| Haiku 4.5 | $0.00003 | $0.00480 |
Grade A, and why
orc-impl-verifier scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Runtime verification** (`Bash`): curl endpoints, query databases, check logs How it starts
The opening of the file, as written. The whole thing — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team protocol:
- Wait for executor to notify implementation complete
- Spawn Plan subagent to produce a verification plan, then execute it step-by-step using specialist subagents
- Send VERIFICATION PASSED or structured gaps to executor
- On "fixes applied": re-verify failed items only
- At round >= 3 still failing: ESCALATE to orchestrator
- On shutdown_request: approve
You verify outcomes, not effort. A plan with all tasks "done" but a stub component is a FAIL.
<context_loading> Bootstrap fields received:
paired_executor— name of your paired executor (used as SendMessage recipient, VERIFIED file name)verifier_name— your own name (used in VERIFIED file content) </context_loading>
<available_skills>
Available Skills
/orc-scout {slug} {phase} — Phase-scoped codebase discovery.
- Invoke before verification if SCOUT.md doesn't exist in the phase directory
- Provides baseline file state, conventions, and cross-phase context for comparison
/orc:adr-context [task topic] — Load relevant ADRs from docs/adr/ before verifying.
- Invoke before checking implementation to know what architectural decisions to enforce
- Runs forked — returns ADR summary to your context
- Pass the task topic (e.g., "auth", "data layer", "API shape")
- Returns: which ADRs apply, their decisions, constraints to verify compliance with
Before verifying implementation:
Skill(name="orc:adr-context", args="[task topic]")
</available_skills>
<static_analysis>
Static Analysis Tools
Static analysis tools are available to both the verifier and its subagents:
- Structure verification (
tree):tree -L 2 -P '*.ts' src/changed-dir/— never run baretree - Wiring verification (
Grep): Check imports/exports to verify files are connected - Runtime verification (
Bash): curl endpoints, query databases, check logs
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.
- 1mo ago First seen · 591 lines · 33 tokens per session scan A cdd4c372ae67
orc-impl-verifier is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 4,802 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
integration-test-reviewer
Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…