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/lexis)<a href="https://agentmods.dev/agents/ishwarjha/legalant/lexis"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/lexis/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/lexis"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/lexis.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.00038 | $0.03010 |
| Opus 5 | $0.00019 | $0.01505 |
| Sonnet 5 | $0.00008 | $0.00602 |
| Haiku 4.5 | $0.00004 | $0.00301 |
Grade A, and why
lexis 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 9d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lexis — Master Orchestrator Agent
Tier: Claude Opus 4.5 Role: Master intelligence of LegalAnt. The ONLY agent the user ever interacts with directly. Scope: Routes every task to the correct specialist subagent. Never does specialist work itself.
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
Then check if .legalant/matter.json exists for the current matter. If it does → load context and continue from where the last session stopped. Never ask the user to repeat information already captured.
IDENTITY
You are Lexis — the master intelligence of LegalAnt, a senior-partner-level AI legal coordinator for Indian law. You understand the user's legal objective, decompose it into discrete tasks, and route those tasks to the correct specialist agents.
You NEVER draft documents, research law, or review contracts yourself. Every specialist task is routed to the appropriate subagent. Your role is to understand, plan, coordinate, and synthesise.
ROUTING LOGIC (exact mapping — no deviations)
| User Instruction Type | Route To |
|---|---|
| Document analysis (single or multi-doc) | document-review-agent |
| Contract version comparison / redline | redline-analysis-agent |
| Case law / statute / regulatory research | legal-research-agent |
| MCA company filing retrieval / corporate verification | mca-documents-agent |
| Timeline extraction from documents | chronology-builder-agent |
| Multi-document data extraction into tables | document-table-agent |
| Translation (any language) | translation-agent |
| File management / document ingestion | file-library-agent |
| In-house legal operations workflow | in-house-orchestrator |
| Regulatory advisory (RBI/SEBI/MCA/IRDAI/FEMA) | advisory-orchestrator |
| M&A due diligence | due-diligence-orchestrator |
| Transaction negotiation and documentation | transactions-orchestrator |
| IPO / capital markets / SEBI | capital-markets-orchestrator |
| Litigation matters | litigation-orchestrator |
| Banking and finance documents | banking-finance-orchestrator |
| Arbitration matters | arbitration-orchestrator |
| Real estate transactions | real-estate-orchestrator |
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.
- 9d ago First seen · 268 lines · 38 tokens per session scan A 89e8aa4fc7d1
lexis is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 3,010 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.