What is dd-merger-analyze?

A command that analyzes an announced or rumored acquisition from the viewpoint of an outside observer, such as a banker, analyst, antitrust lawyer, board member, or journalist. An acquisition is when one company buys another.

Use `/dd-merger-analyze` to study a merger by naming the target and acquirer, with an announcement date or SEC identification numbers when known.

It separates third-party merger analysis from buyer-led deal analysis and gathers the companies needed to examine the transaction.

dd-merger-analyze — Command for Claude Code by ololand-ai

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-analyze/github.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-merger-analyze)

Your own site

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-merger-analyze"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-analyze/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-merger-analyze"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-merger-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 592 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00592
Opus 5	$0.00028	$0.00296
Sonnet 5	$0.00011	$0.00118
Haiku 4.5	$0.00006	$0.00059

Measured 9d ago against content hash 755176ed76f6, 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-analyze 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-analyze.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/dd-merger-analyze

You are creating a third-party merger-analysis deal for an announced or rumored acquisition. The user is an outside observer, not a principal — distinct from /dd-analyze, which assumes the user's firm is the acquirer.

Required inputs

Ask the user for these if any are missing:

target — the company being acquired (free text, e.g. "Discover Financial").
acquirer — the buyer (free text, e.g. "Capital One").

Optional:

announced_date — ISO date (YYYY-MM-DD) of the merger announcement. Used by Lane C to anchor the 8-K window.
target_cik — SEC CIK if known (skips one entity-resolution round-trip).
acquirer_cik — same for the acquirer.

If the user gave a natural-language phrasing ("examine Capital One's acquisition of Discover", "is the X-Y merger accretive?"), parse target + acquirer from it; only ask back if the two companies are not unambiguously identifiable.

Action

Call the OloLand MCP tool analyze_announced_merger with target, acquirer, and optional announced_date / CIKs. The tool returns {deal_id, task_ids, view_url}.
Poll get_merger_readiness(deal_id=...) every ~30 seconds until all three sides (target / acquirer / combined) reach at least medium tier — or until two minutes pass, whichever is sooner.
Surface the deal_id, view_url, and per-side readiness to the user. If any side is still low or missing after polling, name the missing artifacts and suggest manual uploads (8-K, 10-K, S-4, audited financials, market research).
Direct the user to the cockpit (view_url) for the five hero tiles — deal terms, premium analysis, accretion/dilution, antitrust HHI, combined-DCF — plus per-side risk and financial tiles.

Subscription

Runs on Developer as part of the bounded single-deal trial, metered against the monthly credit budget — no longer Pro-gated. Note analyze_announced_merger creates a deal, so a user who has already used their one deal will hit the one-deal-limit CTA. If any call returns tier_gated: true, surface the upgrade CTA at https://app.ololand.ai/settings/billing in your reply.

Read the full file on GitHub · 36 lines

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.

9d ago First seen · 36 lines · 57 tokens per session scan A 755176ed76f6

Subscribe to this mod's changes

dd-merger-analyze is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 592 once invoked, about $0.0003 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.

Finance and fintech

valuation-methods

Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.

agentii-ai/agentii-investment-intelligence · 17 tokens

merit-reconcile

Preview or check the status of Stripe → Merit payout reconciliation (read-only).

Elnora-AI/elnora-merit-aktiva · 20 tokens

audit-checklist

Perform an internal audit, review controls, or prepare for an external financial audit.

GAJETOso/financeskills · 15 tokens

scan

Scan AWS account for cost optimization.

prajapatimehul/claude-aws-cost-saver · 6 tokens

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…

glassity/agent-skills · 64 tokens

audit

Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.

eternal-roman/ledger · 0 tokens