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/assumption-controls)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/assumption-controls"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/assumption-controls.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.00030 | $0.00983 |
| Opus 5 | $0.00015 | $0.00491 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
assumption-controls 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assumption Controls
Underwriting assumptions are first-class controls in OloLand. An analyst owns each statement, with a status (unverified / verified / mitigated / invalidated / accepted) and priority (low / medium / high / critical). Open high/critical tracked assumptions block IC approval; resolving them clears the gate.
This command walks the assumption ledger for a deal and reports the IC-blocker state.
Usage
/assumption-controls <deal_id> [filter]
Arguments
deal_id(required) — The deal whose assumption controls to review.filter(optional) —open|blocking|resolved|all. Default:blocking(the IC-relevant subset).
Execution
-
Call
get_assumption_control_summarywith thedeal_id. This returnstotal,open_count,resolved_count,blocking_count,ic_blocked,by_status,by_category, and the top-10blocking_assumptions. -
If
ic_blockedis true:- List each blocking assumption with statement, category, priority, status, owner, and sensitivity_score.
- Group by category so the analyst can see where the gaps cluster.
-
Call
get_assumption_evidence_packto retrieve the evidence ledger andquality_flags. For each blocking assumption, surface itsevidence_strength(none / weak / partial / supported) and anymissing_links. -
Call
list_deal_assumptionswithpriority=criticalandpriority=highto verify nothing in the tracked-but-not-blocking state has been overlooked (e.g., suggested assumptions waiting to be promoted). -
Render the result as a structured review:
- IC status: Clear / Blocked (with count)
- Blockers: table of
id,statement,category,priority,status,evidence_strength,missing_links - By category: count of open assumptions per category (financial / commercial / operational / market / legal / regulatory / hr / technical / financing / growth / margin / capex / wacc / terminal / other)
- Recommended next actions: for each blocker, the most concrete next step (verify with X document; mitigate via Y; mark accepted with a risk-acknowledgment note; invalidate if the underlying premise no longer holds).
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 · 72 lines · 30 tokens per session scan A 0f48cf278304
assumption-controls is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 983 once invoked, about $0.0002 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.