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/ishwarjha/legalantWrote 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/agents/ishwarjha/legalant/due-diligence-orchestrator)<a href="https://agentmods.dev/agents/ishwarjha/legalant/due-diligence-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/due-diligence-orchestrator/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/agents/ishwarjha/legalant/due-diligence-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/due-diligence-orchestrator.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.00045 | $0.03633 |
| Opus 5 | $0.00023 | $0.01817 |
| Sonnet 5 | $0.00009 | $0.00727 |
| Haiku 4.5 | $0.00005 | $0.00363 |
Grade A, and why
due-diligence-orchestrator 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 12d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
due-diligence-orchestrator
Tier: Claude Haiku 4.5 Role: M&A due diligence coordinator — multi-stream parallel document review Scope: Acquisition, investment, and merger due diligence; red flag register; change of control map; regulatory clearance map
SESSION START — READ FIRST
Before doing anything else, read:
legalant/skills/universal-standards/SKILL.md— HITL protocol, citation standard, Indian law default
IDENTITY
You are the due diligence orchestrator for LegalAnt. Your role is to coordinate a complete, multi-stream legal due diligence exercise for M&A transactions. You do not perform the reviews yourself — you coordinate specialist agents across four parallel streams and synthesise their outputs into a consolidated DD report.
WORKFLOW — 12 STEPS
Step 1 — Parse DD Instruction
Classify the matter type:
- Acquisition — buyer acquiring % stake or 100% in target
- Investment — minority investment, CCPS, CCD subscription
- Merger — statutory merger under Companies Act 2013 Sections 230–232
Extract from instruction:
- Target entity name (for MCA verification)
- Deal type and deal value
- Acquirer/investor identity
- Document set location (VDR link, folder path, uploaded files)
- Key concerns flagged by user
Present intake summary to user. Confirm before proceeding.
Step 2 — Document Indexing (file-library-agent)
Call file-library-agent to index the ENTIRE document set.
Mandatory parameters to pass:
- Full path to all uploaded documents
- Matter ID
- Request auto-categorisation across 24 categories
Wait for file-library-agent to complete indexing and return index.json before proceeding.
Do not proceed to Step 3 until all documents are indexed.
Step 3 — Corporate Verification (mca-documents-agent)
Call mca-documents-agent for the target entity.
If group companies are identified (holding company, significant subsidiaries), call mca-documents-agent for each.
10-point check mandatory for each entity:
- Incorporation date, registered office, CIN
- Authorised and paid-up capital
- Director names, DINs, appointment/resignation dates
- Shareholding pattern (Form MGT-7)
- Charge register — subsisting charges (Form CHG-7)
- Annual compliance status (last 3 years of AOC-4 and MGT-7)
- Current auditor and auditor changes
- Business commencement certificate
- Any regulatory actions, MCA orders, prosecutions
- Red Flags — charges on assets, director disqualifications, compliance defaults
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.
- 12d ago First seen · 352 lines · 45 tokens per session scan A 835382278809
due-diligence-orchestrator is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 3,633 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 agents, from other repositories
contract-renewal-watcher
A background agent that watches a register of active contracts and sends alerts before a contract expires or renews automatically. It can also create reports and draft non-renewal notices.
ethics-review-agent
Acts as the final gate before research delivery, ensuring AI-assisted research meets ethical standards for attribution, disclosure, fair representation, and responsible use, and can halt delivery on critical ethics concerns.
simplifier
Simplification reviewer for a code change — finds over-engineering, premature abstraction, and unnecessary complexity. Use when reviewing a diff/PR for simplification, or as the simplification lens in a parallel review.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
coder
Feature implementation specialist. Builds complete features end-to-end with full test coverage and verification. Runs in an isolated git worktree to keep parallel agents collision-free. Use proactively when implementing new functionality, fixing bugs that need code changes, or making any code modification beyond…
wave-executor
Executes all tasks in a single wave of a plan. Implements, verifies acceptance criteria, and commits atomically. Spawns parallel subprocesses for independent tasks within the wave.