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 commands/ololand-ai/ololand-plugins/risk-reportgit 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/risk-report)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/risk-report"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/risk-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.00033 | $0.01145 |
| Opus 5 | $0.00016 | $0.00573 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
risk-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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Report
Generate a comprehensive risk assessment using OloLand's institutional risk taxonomy — 311 risk factors across 67 categories.
Usage
/risk-report <deal_id> [category]
Arguments
deal_id(required) — The deal ID to assess.category(optional) — Focus on a specific risk dimension:commercial,financial,legal,hr,tech. Default: all.
Execution
- Fetch existing risks with
get_deal_risksfrom the MCP server. - For each risk, retrieve evidence with
get_evidence_links. - Call
find_similar_dealsfor institutional patterns from past deals. If it returnsstatus: "no_usable_corpus", omit the historical-patterns section entirely — do not fabricate one. - Build the report:
- Risk heatmap: Probability vs. impact matrix for top 10 risks
- Category breakdown: Risks grouped by dimension (Commercial, Financial, Legal, HR, Tech)
- Evidence citations: Source documents for each risk
- Historical patterns (only if usable cohort exists): "In 8 similar deals, this risk category was accurate 82% of the time"
- Deal-killer flags: Risks where system severity <= 2 but analysts historically corrected to >= 4
Probability rendering (STRICT)
get_deal_risks now returns three probability metadata fields per risk: probability_source, probability_confidence, and probability_rendering. Honor probability_rendering:
numeric— renderprobability_percentas a percentage (e.g. "65%"). The probability is source-supported.qualitative— render as Low / Medium / High. The probability is a severity proxy, NOT a source-supported number. Do NOT show a percentage in this case.
Mixing severity-derived probabilities with source-supported ones in the same percentage column is a false-precision bug; the rendering field exists specifically to prevent that.
Report Format
Present as structured markdown with:
- Summary table (risk name, severity 1-5, probability per the rendering rule above, dollar impact, evidence source)
- Color-coded severity indicators
- Institutional memory section (patterns from similar deals; omit if no usable cohort)
- Recommended mitigants for Critical/High risks
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 · 91 lines · 33 tokens per session scan A 56f5ea4d531b
risk-report is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,145 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
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
monitor
AML transaction monitoring and suspicious activity reporting.
tax-planning
Optimize tax liability or ensure tax compliance.
filings
Scan recent filings on a company and surface material events (director changes, new charges, capital events, insolvency markers). Works on GB / IE / CA / IS / FI / IM / LI / MX / KR.
child-support-calc
養育費・婚姻費用を令和元年改定算定方式で決定論的に計算.
mca
Run a 10-point MCA company check via the MCA portal.