verify

verify is a command for coding agents from Manavarya09/design-extract. It costs 31 tokens per session (312 once invoked), scanned A, original, MIT.

A verification command that rebuilds a page from extracted design tokens and compares it with the live website. It reports how faithfully the tokens reproduce the original design.

In plain words
What is it for?
Use it to validate extracted JSON or CSS tokens, inspect visual differences, set a fidelity threshold in CI, and verify a site’s design system.
Why use it?
It checks whether an extraction actually captured the important visual details instead of relying on assumptions. It also identifies the largest differences and can enforce a minimum score in automated builds.

Command

Part of the designlang plugin — 2 skills, 14 commands shipped together

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 commands/manavarya09/design-extract/verify
Clone the repo
git clone --depth 1 https://github.com/Manavarya09/design-extract

Or install designlang, the plugin that ships this one along with the rest of its 2 skills, 14 commands.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/manavarya09/design-extract/verify.svg)](https://agentmods.dev/commands/manavarya09/design-extract/verify)
Your own site
<a href="https://agentmods.dev/commands/manavarya09/design-extract/verify"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00031 $0.00312
Opus 5 $0.00015 $0.00156
Sonnet 5 $0.00006 $0.00062
Haiku 4.5 $0.00003 $0.00031

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

Security

Grade A, and why

verify 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.

commands/verify.md · 32 lines

What it actually says

Run designlang verify to close the extraction loop. It rebuilds a page from the extracted design tokens, renders it, pixel-diffs that render against the live site, and reports a fidelity score — how faithfully the tokens reproduce the real design.

npx designlang verify $ARGUMENTS

If no $ARGUMENTS were supplied, ask the user which URL to verify.

After the run completes, surface the fidelity score and the biggest divergences (where the rebuilt page drifts from the live site). This is the honest "did we actually capture it?" signal.

Useful flags via $ARGUMENTS:

Flag Effect
--min <score> exit non-zero if fidelity is below this (CI gate)
--tokens <file> verify against a local tokens file (.json or .css) instead of a fresh extraction

Use --min in CI to fail a build when a design change drops fidelity below a threshold. Pair with /site <url> to verify the whole-site canonical system.

Full reference: https://github.com/Manavarya09/design-extract#full-cli-reference

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. 4d ago First seen · 32 lines · 31 tokens per session scan A e630b0620c42

Subscribe to this mod's changes

verify is a command published in the GitHub repository Manavarya09/design-extract (4,000 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 312 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-30.