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/precedentsgit 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/precedents)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/precedents"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/precedents.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.00031 | $0.00771 |
| Opus 5 | $0.00015 | $0.00385 |
| Sonnet 5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
precedents 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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Precedent Deals
Search OloLand's public M&A corpus for market context and precedent transactions — "who has bought companies like this, when, and roughly for how much".
Usage
/precedents <query> [min_ev=$M] [max_ev=$M] [from=YYYY] [to=YYYY] [outcome=completed|terminated] [sector=...]
Arguments
query(optional) — free text matched against deal summaries and company names.min_ev/max_ev(optional) — enterprise-value band, in millions.from/to(optional) — announcement-year range.outcome(optional) —completedorterminated. Omit for any/unresolved.sector(optional) — one SEC SIC division:agriculture,mining,construction,manufacturing,transport_utilities,wholesale,retail,finance_insurance_real_estate,services,public_administration.
Execution
- Call
mcp__ololand__search_precedent_dealswith the mapped arguments. Caplimitat 25; if the user wants a specific ordinal offset for citations across a multi-step research turn, passcitation_start_numberaccordingly (shared counter withsearch_deal_documents). - This is PUBLIC filing data covering the whole market — not this firm's own deals. If the user actually means the firm's pipeline ("our deals like this one"), use
/similar-dealsorcompare_deals_by_attributeinstead; do not silently redirect without saying so. - Read the returned
corpus_coveragenote before drawing any conclusion from an empty result or a null field. ANULLpremium, target financial, or multiple means "not disclosed in the source filing," never "zero." Outcome and close data are still being backfilled — a missingoutcomemeans unresolved, not that the deal failed to close. - Do not assert a sector or period has no comparable deals from an empty page alone; report what the query found and what the corpus note says about coverage.
Citing
Every deal with a source filing carries a citation_number — use it for claims about the transaction itself (parties, dates, outcome). For a PREMIUM, MULTIPLE, or TARGET FINANCIAL specifically, cite valuation_citation_numbers[<field>] instead — it numbers the exact filing URL substantiating that value, which is often a different filing from citation_number. Both live in one [N] namespace. A value absent from valuation_citation_numbers, or a deal with no citation_number, has no openable source — do not attach a bracket-number marker to it.
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.
- 4d ago First seen · 44 lines · 31 tokens per session scan A 639daef59e6c
precedents is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 771 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.