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/dd-merger-readiness)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-merger-readiness"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-readiness/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/dd-merger-readiness"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-readiness.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.00023 | $0.00420 |
| Opus 5 | $0.00012 | $0.00210 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
dd-merger-readiness 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 9d 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.
What it actually says
/dd-merger-readiness
Report data-readiness tier for each side of a third-party merger-analysis deal so the user knows which engines are safely callable.
Required input
- deal_id — the merger-analysis deal ID (starts with
merger_). Ask if missing.
Action
-
Call
get_merger_readiness(deal_id=...). The tool returns a dict keyed by side with this shape per side:{ "side": "target" | "acquirer" | "combined", "tier": "high" | "medium" | "low" | "missing", "has_filings": bool, "has_audited_financials": bool, "has_market_research": bool, "document_count": int, "source_quality_score": float } -
Render a compact 3-row summary (target / acquirer / combined) with tier label and document_count.
-
If any side is
lowormissing, list the missing artifacts (10-K / 10-Q / 8-K / audited financials / market research) and tell the user where they typically come from. Suggest uploads viaupload_deal_document(deal_id=..., deal_side="target"|"acquirer"|"combined"). -
If all three sides are
mediumor higher, point the user at the four merger engines that are safe to run:/dd-merger-rerun-math.
Subscription
Zero-credit read — works on any tier including Developer. The heavy engines (premium / accretion / DCF / HHI) now also run on Developer as part of the bounded single-deal trial, metered against the monthly credit budget — they are no longer Pro-gated. Only the saleable Forensic Screen PDF (generate_forensic_screen_pdf) is paid.
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.
- 9d ago First seen · 38 lines · 23 tokens per session scan A 07e52c825b48
dd-merger-readiness is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 420 once invoked, about $0.0001 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…
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.