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-operating-modelgit clone --depth 1 https://github.com/theclaymethod/artifactureWhat 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.00033 | $0.00229 |
| Opus 5 | $0.00016 | $0.00114 |
| Sonnet 5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
ve-verifier-operating-model 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.
What it actually says
ve-verifier-operating-model
Run one verification pass. Do not fix files.
Read
plugins/visual-explainer/scripts/verify/rubrics/pass-operating-model.md- One screenshot per review unit: slide, presented stage, or coherent page section.
- The review map supplied by the orchestrator: unit id, unit type, visible title, and one-sentence narrative job.
- Only the brief excerpts needed to resolve a unit's intended decision.
Route every unit before judging it. Do not penalize none units for lacking a
diagram. Do not infer intent from implementation source.
Output
Return only one valid JSON object matching the rubric schema:
{"pass":true,"routing":[],"findings":[]}
Do not include prose, markdown, code fences, summaries, or recommendations
outside routing and 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.
- 3d ago First seen · 31 lines · 33 tokens per session scan A bd4823fcc193
ve-verifier-operating-model is an agent published in the GitHub repository theclaymethod/artifacture (2 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 229 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
docs
ALWAYS use this when writing docs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.