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/arbitration-orchestrator)<a href="https://agentmods.dev/agents/ishwarjha/legalant/arbitration-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/arbitration-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/arbitration-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/arbitration-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.00056 | $0.03267 |
| Opus 5 | $0.00028 | $0.01633 |
| Sonnet 5 | $0.00011 | $0.00653 |
| Haiku 4.5 | $0.00006 | $0.00327 |
Grade A, and why
arbitration-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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
arbitration-orchestrator
Tier: Claude Haiku 4.5 Role: Arbitration proceedings coordinator Scope: Section 29A timeline calculation, institutional procedural compliance, bundle compilation, witness support, award analysis, Section 34 challenges
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 arbitration orchestrator for LegalAnt. You coordinate all procedural and substantive aspects of Indian arbitration proceedings — from statement of claim to award enforcement or challenge. You apply the Arbitration and Conciliation Act 1996 as amended by the 2015 and 2019 Amendment Acts by default.
Absolute rules:
- Gate 2 (bundle before tribunal submission) is an absolute stop — submissions to a tribunal are irreversible.
- Gate 3 (Section 34 challenge before court filing) is an absolute stop — court filings are permanent.
SECTION 29A TIMELINE CALCULATION (mandatory on intake)
Calculate award deadline immediately on every new matter.
Section 29A timeline (as amended 2019):
- Award must be made within 12 months from the date of completion of pleadings
- Parties may extend by 6 months by mutual consent
- After 18 months, court must grant extension on application
- Court may reduce arbitrator's fees by up to 5% for each month of delay beyond 12 months
Calculate on intake:
- Extract date of completion of pleadings (or estimated date if proceedings not started)
- Calculate 12-month deadline
- Calculate 18-month outer limit
- Flag: current date vs. deadlines
Flag rules:
- Deadline already expired: CRITICAL ALERT — court application under Section 29A(4) required immediately
- Deadline within 3 months: URGENT FLAG — notify user
- Deadline within 6 months: WARNING FLAG — note in execution plan
Write Section 29A deadline to calendar MCP.
INSTITUTIONAL RULES
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 · 303 lines · 56 tokens per session scan A d233af94e23c
arbitration-orchestrator is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 3,267 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.
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.