A verification tool for checking claims and citations in deal documents such as investment memos, CIMs, and valuation write-ups. It compares the text with source documents and, when relevant, rechecks DCF calculations.

It helps verify written deal analysis, audit citation markers, reconcile claims across documents, and check discounted-cash-flow calculations.

It catches unsupported numbers, missing citations, inconsistent documents, and arithmetic errors before an artifact is used.

verify — Command for Claude Code by ololand-ai/ololand-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 54 commands, 3 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/verify/github.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/verify)

Your own site

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/verify"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/verify/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/verify"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,392 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00095	$0.01392
Opus 5.5	$0.00038	$0.00557
Sonnet 5.5	$0.00019	$0.00278
Haiku 4.5	$0.00010	$0.00139

Measured 1mo ago against content hash d846395049e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/ololand-dd/commands/verify.md · 81 lines

How it starts

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

/verify

You are running OloLand's verifier stack against an artifact and a deal. This is the user-facing surface for the four atomic-claim verifiers that back the "verifiable outputs" guarantee.

Required inputs

Ask the user for these if missing:

deal_id — the OloLand deal whose source documents back the verification.
text — the artifact text to verify. Accept any of:
- A paragraph or section pasted inline.
- A path to a local file (read it with your file tool, then pass the contents).
- The output of a previous OloLand command (e.g., the IC memo body, a CIM section, a risk narrative).

Optional:

include_dcf_arithmetic (default true) — also replay the DCF identity checks against the deal's stored DCFRun. Set to false if the artifact does not reference a DCF.
audit_markers (default true when the artifact contains [N] markers) — also run check_citation_coverage to audit the [N] markers.

Action

Call mcp__ololand__run_atomic_verifiers with deal_id, text, and include_dcf_arithmetic.
If the artifact contains any [N] markers, also call mcp__ololand__check_citation_coverage with the same deal_id and text. (Detect with a quick regex on the text — \[\d+\] excluding [EK:N].)
If the user signals this is an IC memo or final report (i.e., wants a full audit, not just a spot-check), also call mcp__ololand__reconcile_documents with deal_id. This walks the CPA > tax > management > AI source hierarchy across the deal's stored financial observations.

Externally-drafted artifacts (e.g. written in Claude Cowork)

The verifiers above are tuned for OloLand-produced text. When the user pastes an artifact drafted outside OloLand — a memo written in Claude Cowork, a draft from another tool, a partner's marked-up paragraph — grade it per-claim against the deal's ingested data room instead:

Call mcp__ololand__grade_external_artifact with artifact_text, deal_id, and mode (strict default; lenient for early drafts). Optionally pass a rubric string to steer what "supported" means.
For each figure and claim, the tool retrieves evidence per-claim from the deal's corpus (hybrid search) and returns a PASS / FAIL / UNVERIFIED verdict — it confirms a claim against the real source, or surfaces a contradicting source the author never cited. It also returns a content-hashed provenance pack for IC lineage.
Handle the nudge responses honestly, don't paper over them:
- needs_deal (no deal_id) — the artifact can't be graded without a deal to grade against. Offer to create_deal and upload the data room first (this is the intended OloLand adoption path from Cowork).
- needs_corpus (deal exists but empty) — ingest the data room before grading; there's nothing to retrieve against.

Read the full file on GitHub · 81 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.

1mo ago First seen · 81 lines · 95 tokens per session scan A d846395049e9

Subscribe to this mod's changes

verify is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,392 once invoked, about $0.0004 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-09-03.

Finance and fintech

verify

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/verify

Required inputs

Action

Externally-drafted artifacts (e.g. written in Claude Cowork)

What this file has done since we first saw it

Other commands, from other repositories

analyze-bond-rv

valuation-methods

merit-reconcile

cost-per-task

audit-checklist

scan