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.
npx agentmods add skills/ololand-ai/ololand-plugins/verifier-stacknpx skills add ololand-ai/ololand-plugins --skill verifier-stackgit clone --depth 1 https://github.com/ololand-ai/ololand-pluginsWrote 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/skills/ololand-ai/ololand-plugins/verifier-stack)<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/verifier-stack"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/verifier-stack.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 | $0.00092 | $0.01339 |
| Opus 5 | $0.00046 | $0.00669 |
| Sonnet 5 | $0.00018 | $0.00268 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
verifier-stack 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifier Stack
OloLand's verifier stack mechanically checks that every number in an artifact is supported by the deal's source documents, that every citation marker points at a real retrievable chunk, and that the deal's stored DCF identities hold. It is the "defend every number, cite every source" guarantee in code, not in marketing copy.
What the verifiers actually do
verify_inline_numbers
Extracts every dollar amount and every percentage from the artifact text. For each number, checks whether it appears (within 5% relative / 0.5pt absolute tolerance) in at least one chunk retrieved from the deal corpus.
- Catches: fabricated revenue figures, transposed digits (e.g. $34.2M vs $32.4M), unit drift (
$304Kreported as$304M). - Misses: numbers that happen to appear in the corpus by coincidence (e.g. a generic "$1M" mentioned in a risk factor section); numbers that are derived but never raw in the source (e.g. growth rates the analyst computed correctly but the chunk only shows the underlying revenues).
verify_claim_chunks
Stricter than verify_inline_numbers. Splits the text into sentences containing financial numbers. A sentence passes only when all of its numbers can be matched in a single chunk.
- Catches: sentences that stitch together unrelated numbers from different sources (a tell for hallucinated synthesis).
- Misses: the same coincidence cases as above.
verify_citation_existence
For artifacts that use the legacy [Source: file=..., p.N] block format: extracts every block and validates that the filename exists in the deal's document set (with fuzzy matching) and the cited page is in range.
- Catches: invented filenames, wrong page numbers.
- Skipped: when the artifact uses the modern
[N]marker format only — that's audited bycheck_citation_coverage.
verify_dcf_arithmetic
Replays the two DCF identities against the deal's most recent DCFRun:
enterprise_value == pv_fcf_sum + pv_terminal_valueequity_value == enterprise_value - net_debt
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.
- today First seen · 84 lines · 92 tokens per session scan A bdc34522b74e
verifier-stack is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 92 tokens to every session and 1,339 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…