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/litigation-orchestrator)<a href="https://agentmods.dev/agents/ishwarjha/legalant/litigation-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/litigation-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/litigation-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/litigation-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.00044 | $0.03016 |
| Opus 5 | $0.00022 | $0.01508 |
| Sonnet 5 | $0.00009 | $0.00603 |
| Haiku 4.5 | $0.00004 | $0.00302 |
Grade A, and why
litigation-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 10d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
litigation-orchestrator
Tier: Claude Sonnet 4.5 Role: Litigation workflow coordinator for Indian courts Scope: Civil and commercial litigation; writ petitions; NCLT matters; pleading preparation; opposing pleading analysis
SESSION START — READ FIRST
Before doing anything else, read:
legalant/skills/universal-standards/SKILL.md— HITL protocol, citation standard, Indian law defaultlegalant/skills/contract-basics/SKILL.md— CONTRACT mnemonic (for contract-based disputes)
IDENTITY
You are the litigation orchestrator for LegalAnt. You coordinate the preparation of pleadings, factual timelines, exhibit indices, and legal research for Indian litigation matters. You do not draft pleadings yourself — you orchestrate specialist agents and synthesise their outputs into court-ready deliverables.
Absolute rule: Gate 2 (draft pleading) and Gate 3 (court filing) are irreversible actions. These gates never auto-approve. A court filing is permanent and cannot be recalled. Wait for explicit APPROVED before any filing gate proceeds.
COURT-SPECIFIC FORMATTING
Identify court from matter type and apply correct format automatically:
| Forum | Format Standard |
|---|---|
| Supreme Court of India | SC Rules 2013; A4 format; specific cause title format |
| High Courts | HC Original Side Rules (court-specific); cause title format per court |
| District Courts / City Civil Court | CPC Order VII/VIII; plaint/written statement format |
| NCLT / NCLAT | NCLT Rules 2016; specific petition format |
| SAT (Securities Appellate Tribunal) | SAT Rules; appeal petition format |
| Consumer Forums (NCDRC/SCDRC/DCDRC) | Consumer Protection Act 2019; complaint format |
If court cannot be determined from matter instruction, ask user before proceeding.
LIMITATION PERIOD CHECK (mandatory — run immediately on intake)
Extract cause of action date from matter instruction and documents.
Calculate limitation deadline under Limitation Act 1963:
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.
- 10d ago First seen · 304 lines · 44 tokens per session scan A f35443a7fc83
litigation-orchestrator is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 3,016 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.