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/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/commands/ololand-ai/ololand-plugins/verification-marketplace)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/verification-marketplace"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/verification-marketplace/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.
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/verification-marketplace"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/verification-marketplace.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00588 |
| Opus 5.5 | $0.00013 | $0.00235 |
| Sonnet 5.5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
verification-marketplace 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Marketplace
Use this command when the user asks for a human reviewer, verified forensic screen, CPA-style sign-off, external reviewer status, or IC appendix provenance.
Usage
/verification-marketplace <deal_id> [status|list|request]
Arguments
deal_id(required) - The deal whose forensic screen verification state should be reviewed.action(optional) -status(default),list, orrequest.
Execution
- Call
get_deal_verification_status(deal_id)first. This returns the active request, latest signed sign-off if one exists, reviewer credential metadata, and web URLs. - If action is
list, calllist_deal_verification_requests(deal_id)and render each request withstatus,priority,requested_at,assigned_at,completed_at,source_artifact_id, andforensic_job_id. - If action is
request, confirm the user wants to queue a Phase-1 concierge review. Then callrequest_verified_forensic_screenwith thedeal_idand any knownpurchase_id,forensic_job_id,source_artifact_id, andfindings_scope. - If a signed artifact exists, surface its signed artifact ID and IC-package appendix lineage. Treat this as control evidence, not generic services copy.
Output
Render:
- Verification state - no request / queued / assigned / in review / signed / rejected / canceled.
- Reviewer - reviewer name, credential, firm, and conflict status when available.
- SLA - requested/assigned/completed timestamps and any SLA deadline returned by the tool.
- Signed artifact lineage - parent forensic artifact -> signed verification artifact -> IC appendix.
- Next action - queue request, wait for assignment, review signed statement, or attach to IC package.
Guardrails
- Do not imply automatic payment, escrow, or instant fulfillment. Phase 1 is a manual concierge marketplace with explicit fee/spread accounting.
- Do not bypass conflict checks. If the tool reports a conflict or blocked assignment, surface that as a blocker.
- If the user wants to approve IC, pair this command with
/ic-approve-readiness; human verification is additional evidence, not a substitute for resolving assumption-control blockers.
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 · 49 lines · 32 tokens per session scan A 7b408b0f776a
verification-marketplace is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 32 tokens to every session and 588 once invoked, about $0.0001 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.
Other commands, from other repositories
analyze-bond-rv
Analyze a bond's relative value vs yield curves and credit spreads with scenario stress testing.
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).
cost-per-task
Compute cost-per-successful-task unit economics from usage and cost data, including retries, failures, and quality thresholds.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.