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/dd-analyzegit 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-analyze)<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>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.00048 | $0.01110 |
| Opus 5 | $0.00024 | $0.00555 |
| Sonnet 5 | $0.00010 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
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.
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
- Verify the deal exists using the
get_dealMCP tool. - 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 originaltask_idreturned by an earlierrun_due_diligencecall and callcheck_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 substituteget_analysis_run_status, because it reads a different canonicalAnalysisRunworkflow. Stop after reporting status. - Call
run_due_diligence(deal_id)exactly once. The backend dispatchesmaster_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
- Poll the returned parent
task_idwithcheck_task_status, but treatSUCCESSonly 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. - After launch confirmation, read
get_financial_snapshotandget_deal_risksseparately:- Record the request time before invoking
run_due_diligence. Treat the financial leg as fresh only when the returned snapshot'screated_atis at or after that request time. Otherwise report it as pending or stale. get_deal_risksexposes 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_tilesmay be read separately when useful, but do not claim this extraction run created or refreshed those tiles.
- Record the request time before invoking
- 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/unverifiedand the exact missing proof.
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.
- 5d ago First seen · 59 lines · 48 tokens per session scan A 6fea5a098254
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.
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.