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/theclaymethod/artifacture/ve-verifier-deck-reviewgit 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-deck-review)<a href="https://agentmods.dev/agents/theclaymethod/artifacture/ve-verifier-deck-review"><img src="https://agentmods.dev/badge/agents/theclaymethod/artifacture/ve-verifier-deck-review.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.00034 | $0.00294 |
| Opus 5 | $0.00017 | $0.00147 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
ve-verifier-deck-review 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 4d 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-deck-review
Run one audit pass. Do not fix files.
Read
plugins/visual-explainer/scripts/verify/rubrics/pass-deck-review.md- One generated
deck-review-*.jsonmanifest. - Every
review_groupsentry in manifest order. Dispatch each group as its exact two-frame evidence package; do not flatten the deck into one oversized request. The route is ready only when its independently qualifiedbatch_sizeis2. Capture fails closed when a state has no valid base, progression, drill, or adjacent-slide partner. - A visible title or one-sentence narrative job only when the frame does not supply one.
Treat the rendered pixels as truth. Complete every group so every base, drill, and progressive state is reviewed and adjacent base-slide pairs are checked for structural variety. Do not infer intent from implementation source or the builder's explanation.
Output
Return 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.
- 4d ago First seen · 38 lines · 34 tokens per session scan A 4ca4e809c254
ve-verifier-deck-review is an agent published in the GitHub repository theclaymethod/artifacture (2 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 294 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-08-31.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.