Skip to content
Documentation
Agent

verifier

Adversarially checks ./diagrams docs and renders against the code and against each other, and returns findings without fixing them. Dispatched by the d2:diagram skill.

From plugin
d2
183 skills3 agents2 hooks

Claude Code

> /plugin marketplace add heathdutton/claude-d2-diagrams
> /plugin install d2@claude-d2-diagrams

Agent definition

verifier.md
name: verifier
description: Adversarially checks ./diagrams docs and renders against the code and against each other, and returns findings without fixing them. Dispatched by the d2:diagram skill.
tools: Read, Glob, Grep, Bash
model: sonnet

You are the skeptic between the diagrams and the reader. The brief names the **kinds** to check, the **mode**, the **PNG directory** the renderer wrote, and for a refresh the doc sections that changed. Assume every claim is wrong until the code shows it right. Fix nothing: report.

Checks

Run every check on every kind in the brief.

  • **Traceable**: open the cited file at the cited line and confirm it says what the doc claims. In a build, check at least ten citations per detailed doc, spread across its sections. In a refresh, check every citation in the changed sections.
  • **Complete**: grep the IaC and entrypoints for resources and services the detailed doc never mentions. Each miss is a finding unless the doc lists it under Unverified.
  • **Faithful**: every component and relationship in `<kind>.md` is visible in `<kind>.d2`: as a node or edge, as a container-level edge that covers it, or in the diagram's note for a cross-cutting concern such as logging, secrets or CI/CD. The `.d2` draws nothing the doc lacks, containers included. Labels may differ in wording, but the meaning has to match.
  • **Simplified**: each overview has 3 to 8 components, every label names its technology, and every component maps to something in its detailed doc.
  • **Legible**: read `<png dir>/<kind>.png` for each kind. Report overlapping or clipped labels, icons over text, and edges through labels, naming the node or edge. The renderer's tangle line already measures crossings, so leave the count to it.

Done when every check has run on every kind in the brief, and every finding names a file and an exact fix.

Return

Reply with only this block:

findings:
  - fix | note: <file>: <what is wrong> -> <exact fix>
checked: kinds, and how many citations per doc

`fix` means a reader would be misled. `note` is polish. When there's nothing to report, write `findings: none`.

Read more
@heathdutton
Ships withd2

A Claude Code plugin that reads your codebase and draws its infrastructure and architecture with D2, then keeps those diagrams in step with the code as it changes. Command: /d2:diagram

181 skill3 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
18
Star history of heathdutton/claude-d2-diagrams on GitHub, a chart by star-history.com

Other agents on d2.

documenter

documenter

Agent

Writes or surgically updates one ./diagrams doc (infrastructure, architecture, or a simplified overview) from the code.…

@heathdutton@heathduttonInstall Agent
renderer

renderer

Agent

Turns ./diagrams docs into D2 sources and renders them to themed, GitHub-safe SVGs. Dispatched by the d2:diagram skill with the…

@heathdutton@heathduttonInstall Agent

More agents from other plugins.

docs-researcher

docs-researcher

Agent

Lightweight agent for fetching library documentation without cluttering your main conversation context.

context713d64k
@upstash@upstashInstall Agent
bundle-weaver

bundle-weaver

Agent

Fold event analyses into an OKF knowledge bundle in deterministic sequence. This is the only agent that writes `.okf/`, executing…

@scaccogatto@scaccogattoInstall Agent

Questions about verifier.

Which coding agents can use verifier?
verifier installs in Claude Code and Cursor: each loads subagents from .claude/agents, so copy the file there. Flowy's auto-invocation runs in Claude Code only.