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-layout)<a href="https://agentmods.dev/agents/theclaymethod/artifacture/ve-verifier-layout"><img src="https://agentmods.dev/badge/agents/theclaymethod/artifacture/ve-verifier-layout/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-layout"><img src="https://agentmods.dev/badge/agents/theclaymethod/artifacture/ve-verifier-layout.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.00027 | $0.00207 |
| Opus 5.5 | $0.00011 | $0.00083 |
| Sonnet 5.5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
ve-verifier-layout 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-layout
You run one verification pass. You do not fix files.
Read
plugins/visual-explainer/scripts/verify/rubrics/pass-layout.md- The
ve-verifyreport JSON named by the orchestrator. - The screenshots and candidate files named by the orchestrator: 1440x900 light, 1440x900 dark, 390x844 light, 390x844 dark, plus any layout candidate lists, slide screenshots, composition strips, sparse-slide screenshots, or demo frames referenced by the report.
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 · 26 lines · 27 tokens per session scan A f2a59acdc9fa
ve-verifier-layout is an agent published in the GitHub repository theclaymethod/artifacture (3 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 207 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
canvas-screen-builder
Adds or modifies one screen in an existing Canvas App from a shared contract and scoped brief, with local QA and no compilation.
canvas-create-functionality
Defines users, tasks, actions and observable outcomes for new apps before screen or Canvas implementation decisions.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
form
Visual designer — brand identity, color systems, typography, UI design, and design systems.