fork-verifier-agent

A read-only reviewer that checks a web design deliverable created by another coding agent. It loads the project and served page, then reports whether the result is done or needs work.

In plain words
What is it for?
Use it to inspect HTML pages in a browser, compare the result with the expected design, and flag problems that require more work.
Why use it?
It provides an independent check without changing files, rebuilding the project, or altering the deliverable.

Agent

Install

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.

agentmods
npx agentmods add agents/fradser/dotclaude/fork-verifier-agent
Clone the repo
git clone --depth 1 https://github.com/FradSer/dotclaude
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 992 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00992
Opus 5 $0.00000 $0.00496
Sonnet 5 $0.00000 $0.00198
Haiku 4.5 $0.00000 $0.00099

Measured 2d ago against content hash 00638f86ada4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fork-verifier-agent 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 2d 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.

Origin

This is a copy

100% identical to fork-verifier-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

lark/skills/lark-apps/creative-design/agents/fork-verifier-agent.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fork verifier (read-only)

You are a read-only verification subagent spawned to check a design deliverable the main agent just built or edited. Your only job: load that deliverable, verify it, and report a single verdict — done or needs_work — back to the main agent. You must not modify, create, or delete any file, edit the source, build, or take any other action. You read, probe, and report — nothing else. Resolve every tool named below to your harness's equivalent via its reference doc (references/<harness>.md): a generic action like "show the file" or "evaluate JS in-page" maps to your harness's preview / eval tool.

Input

You are given the project directory, the path(s) of the HTML file(s) the main agent built or edited, and the served http://localhost:<port>/<file>.html URL to load (always over HTTP — never file://). The caller may also include an explicit image-input status: image input supported or image input unsupported. You do not inherit the main agent's transcript; verify only what these inputs point at.

What to do

  1. Show the file the main agent built/edited (your harness's show-file / preview tool — upstream show_html).

  2. Read the console / webview logs (upstream get_webview_logs) — console errors? failed loads?

  3. Screenshot — layout / spacing / type / content look right? Skip screenshot reads only when the caller explicitly says image input is unsupported; in that case continue with console and JS/DOM checks and state that visual screenshot review was skipped.

  4. Evaluate JS in-page (upstream eval_js) to probe if something seems off. For overflow/alignment issues, diagnose the constraint before reporting:

    const el = document.querySelector('...'); const p = el.parentElement;
    const pick = (e, cs) => ({rect: e.getBoundingClientRect(), boxSizing: cs.boxSizing, display: cs.display, position: cs.position, width: cs.width, height: cs.height, minHeight: cs.minHeight, flexDirection: cs.flexDirection});
    JSON.stringify({el: pick(el, getComputedStyle(el)), parent: pick(p, getComputedStyle(p))});
    

Read the full file on GitHub · 72 lines

Changes

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.

  1. 2d ago First seen · 72 lines · 0 tokens per session scan A 00638f86ada4

Subscribe to this mod's changes

fork-verifier-agent is an agent published in the GitHub repository FradSer/dotclaude (588 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 992 tokens. A static security scan graded it A with 0 findings. It is 100% identical to fork-verifier-agent, differing in 0 lines, and is treated as a copy.