dd-merger-readiness

dd-merger-readiness is a command for Claude Code from ololand-ai/ololand-plugins. It costs 23 tokens per session (420 once invoked), scanned A, original, Apache-2.0.

A command that reports whether the available data is sufficient for each side of a merger analysis: the target company, the acquirer and the combined deal. It uses readiness tiers and shows available documents and source-quality details.

In plain words
What is it for?
Use it with a merger deal ID to check filings, audited financials, market research and document counts for each side.
Why use it?
It helps reveal missing or weak data before running analysis engines that could produce unsafe results.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ololand-dd plugin — 22 skills, 52 commands, 3 agents shipped together

Good fit Use it with a merger deal ID to check filings, audited financials, market research and document counts for each side.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ololand-ai/ololand-plugins/dd-merger-readiness
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 52 commands, 3 agents.

Wrote 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.

agentmods badge for dd-merger-readiness

README.md
[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-readiness/github.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-merger-readiness)
Your own site
<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.

agentmods 80×15 button for dd-merger-readiness

Your own site · 80×15
<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>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 07e52c825b48, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

plugins/ololand-dd/commands/dd-merger-readiness.md · 38 lines

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

  1. 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
    }
    
  2. Render a compact 3-row summary (target / acquirer / combined) with tier label and document_count.

  3. If any side is low or missing, 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 via upload_deal_document(deal_id=..., deal_side="target"|"acquirer"|"combined").

  4. If all three sides are medium or 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.

Changes

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.

  1. 9d ago First seen · 38 lines · 23 tokens per session scan A 07e52c825b48

Subscribe to this mod's changes

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.