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/value-impact)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/value-impact"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/value-impact/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/value-impact"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/value-impact.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.00034 | $0.00538 |
| Opus 5.5 | $0.00014 | $0.00215 |
| Sonnet 5.5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
value-impact 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Value Impact
Use this command when the user asks for ROI, hours saved, avoided QoE/advisor cost, value multiple, or the evidence behind OloLand's value-impact claims.
Usage
/value-impact <deal_id>
/value-impact company [start=YYYY-MM-DD] [end=YYYY-MM-DD] [workflow=<workflow_key>]
/value-impact preview workflows=pre_loi_screen,full_qoe deals=12 cost=238800
Execution
- If the first argument is a deal id, call
mcp__ololand__get_deal_value_impact(deal_id). - If the first argument is
companyor the user asks for firm-wide ROI, callmcp__ololand__get_company_value_impactwith any date/workflow filters. - If the user asks "what would this be worth if..." call
mcp__ololand__preview_value_impactwithworkflows,workflow_counts,deals_per_year, and optionalannual_platform_cost_cents. - If the user asks what assumptions drive the ledger, call
mcp__ololand__get_value_impact_assumptions. - Only call
mcp__ololand__update_value_impact_assumptionswhen the user explicitly asks to change company ROI assumptions and confirms the values. That tool is company-admin gated.
Output
Render:
- Value summary: hours saved, labor cost avoided, advisor cost avoided, gross value, net value if platform cost is complete.
- Cost completeness:
ololand_cost_is_complete, missing-cost count, and whethervalue_multipleis known or intentionally withheld. - Top events: workflow, source, completed time, confidence, and methodology note.
- Assumptions: hourly rates, display mode, external QoE baseline when relevant.
- Next action: open the returned
view_url, adjust assumptions, or run the workflow that would create missing events.
Guardrails
- Never convert unknown OloLand cost to zero. If
net_value_centsorvalue_multipleis null because cost is incomplete, say that directly. - Treat the ledger as substantiated estimate, not a guarantee of actual savings.
- Preserve confidence and methodology notes when presenting dollar 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.
- 1mo ago First seen · 42 lines · 34 tokens per session scan A 4d8cb3032b8f
value-impact is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 538 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-08-31.
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.