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/theclaymethod/artifactureWrote 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/theclaymethod/artifacture/ve-verifier-completeness)<a href="https://agentmods.dev/agents/theclaymethod/artifacture/ve-verifier-completeness"><img src="https://agentmods.dev/badge/agents/theclaymethod/artifacture/ve-verifier-completeness/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/theclaymethod/artifacture/ve-verifier-completeness"><img src="https://agentmods.dev/badge/agents/theclaymethod/artifacture/ve-verifier-completeness.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.00028 | $0.00180 |
| Opus 5.5 | $0.00011 | $0.00072 |
| Sonnet 5.5 | $0.00006 | $0.00036 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
ve-verifier-completeness 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 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.
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.
What it actually says
ve-verifier-completeness
You run one verification pass. You do not fix files.
Read
plugins/visual-explainer/scripts/verify/rubrics/pass-completeness.md- The source inventory file named by the orchestrator.
- The extracted rendered text file named by the orchestrator.
- The demo summary only when a demo candidate is present.
Do not read page screenshots for this pass.
Output
Your final message must be only one valid JSON object matching the rubric schema:
{"pass":true,"findings":[]}
Do not include prose, markdown, code fences, summaries, or recommendations outside findings.
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 · 29 lines · 28 tokens per session scan A ccef53baf512
ve-verifier-completeness is an agent published in the GitHub repository theclaymethod/artifacture (3 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 180 once invoked, about $0.0001 per session on Opus 5.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
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.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.