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/ethan-haas/docverify-mcpWrote 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/commands/ethan-haas/docverify-mcp/verify-report)<a href="https://agentmods.dev/commands/ethan-haas/docverify-mcp/verify-report"><img src="https://agentmods.dev/badge/commands/ethan-haas/docverify-mcp/verify-report.svg" alt="Measured on agentmods" 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.00021 | $0.00316 |
| Opus 5 | $0.00010 | $0.00158 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
verify-report 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 6d 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
Run extract_statement from the docverify MCP server on: $ARGUMENTS
Then report, in this order:
- Verdict.
verified: trueorverified: false, and the check count fromverification.checks_run. - If verified — the entity, the fiscal year end, and a table of the line items with one column per fund type. End with "all N checks passed".
- If refused — do NOT report any figure as a value of anything. List each id in
refusal.failed_check_idswith its arithmetic fromfailed_checks, then say that no figures are available for this document because it does not reconcile.
If the caller asks to see the working, follow up with verify_totals on the same path and
show the arithmetic per check. On a refused document only the FAILING checks carry
arithmetic; the rest come back disclosed: false, and that is the contract working, not a
gap to fill in.
extract_statement takes the report PDF. If the caller offers a pre-extracted .json, use
verify_totals instead and say what it does and does not establish: it checks that THEIR
numbers are internally consistent, it does not certify them as the document's figures.
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.
- 6d ago First seen · 26 lines · 21 tokens per session scan A cb25d8da1cbb
verify-report is a command published in the GitHub repository ethan-haas/docverify-mcp (0 stars, last pushed 28d ago), licensed MIT. It adds 21 tokens to every session and 316 once invoked, about $0.0001 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-31.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
archive-ledger
../../../shared/commands/archive-ledger.md.