dd-analyze

dd-analyze is a command for coding agents from ololand-ai/ololand-plugins. It costs 48 tokens per session (1,110 once invoked), scanned A, original, Apache-2.0.

A command that runs a limited due-diligence review for a deal. Due diligence is the process of checking a business before an investment or acquisition; this review covers a financial snapshot, five risk areas, and commercial findings about the target.

In plain words
What is it for?
Run `/dd-analyze <deal_id>` to start the review for a specific deal, or check the status of an earlier run when its task ID is available.
Why use it?
It provides a defined first-pass review while keeping valuation, forensic quality-of-earnings work, conflict checks, war-gaming, and memo writing as separate actions.

Command

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

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.

agentmods
npx agentmods add commands/ololand-ai/ololand-plugins/dd-analyze
Clone the repo
git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

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-analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-analyze.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-analyze)
Your own site
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/dd-analyze"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/dd-analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,110 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00048 $0.01110
Opus 5 $0.00024 $0.00555
Sonnet 5 $0.00010 $0.00222
Haiku 4.5 $0.00005 $0.00111

Measured 5d ago against content hash 6fea5a098254, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

dd-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 5d 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-analyze.md · 59 lines

How it starts

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

Due Diligence Analysis

Run the bounded extraction and risk-analysis pipeline on a deal using OloLand's institutional control system. This command does not run DCF/LBO/Monte Carlo, war-game, forensic QoE, cross-document conflict detection, or memo generation.

Usage

/dd-analyze <deal_id>

Arguments

  • deal_id (required) — The deal ID to analyze. The backend tool does not accept a narrower scope parameter.

Execution

  1. Verify the deal exists using the get_deal MCP tool.
  2. Status-only questions are a terminal read-only path and never start a run. If the user is asking whether an earlier dispatch finished or what it produced, do not continue to step 3 and do not call run_due_diligence. Require the original task_id returned by an earlier run_due_diligence call and call check_task_status(task_id) only to report that task's launch state. If the caller does not have that task ID, report that this legacy dispatch's status is unavailable; do not substitute get_analysis_run_status, because it reads a different canonical AnalysisRun workflow. Stop after reporting status.
  3. Call run_due_diligence(deal_id) exactly once. The backend dispatches master_data_extraction_task, whose bounded contract is:
    • Simplified financial statement extraction into the deal snapshot
    • Risk extraction across the five dimensions: HR, Legal, Tech, Commercial, and Financial
    • Target-only commercial opportunities, insights, and synergies extraction
    • No DCF, LBO, Monte Carlo, war-game, forensic QoE, conflict detector, memo, or other valuation engine
  4. Poll the returned parent task_id with check_task_status, but treat SUCCESS only as launch confirmed. The current parent task dispatches five child jobs asynchronously and returns before they all finish; its terminal state is not an analysis-complete signal.
  5. After launch confirmation, read get_financial_snapshot and get_deal_risks separately:
    • Record the request time before invoking run_due_diligence. Treat the financial leg as fresh only when the returned snapshot's created_at is at or after that request time. Otherwise report it as pending or stale.
    • get_deal_risks exposes the latest available register but does not prove that this legacy dispatch refreshed it. Label those rows latest available risks, not “risks extracted by this run.”
    • This MCP rail exposes no durable completion/read receipt for the three commercial child jobs. Report their completion as unverified; do not attribute existing commercial findings to this run.
    • get_deal_summary_tiles may be read separately when useful, but do not claim this extraction run created or refreshed those tiles.
  6. Never call the parent task “complete” or infer all-child completion from its success. If the freshness checks above do not pass, return launch confirmed; results pending/unverified and the exact missing proof.

Read the full file on GitHub · 59 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.

  1. 5d ago First seen · 59 lines · 48 tokens per session scan A 6fea5a098254

Subscribe to this mod's changes

dd-analyze is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,110 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.