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/commands/ishwarjha/legalant/litigate)<a href="https://agentmods.dev/commands/ishwarjha/legalant/litigate"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/litigate/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/commands/ishwarjha/legalant/litigate"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/litigate.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.00011 | $0.00287 |
| Opus 5 | $0.00005 | $0.00143 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
litigate 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 8d 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.
What it actually says
Invoke the litigation-orchestrator sub-agent for litigation support.
Matter details:
$ARGUMENTS
The agent will:
- Limitation Period Check (mandatory on every intake — Limitation Act 1963)
- Identify the applicable limitation article
- Calculate expiry date from cause of action
- Flag if limitation is at risk (< 30 days)
- Identify court and applicable rules:
- Supreme Court / High Court / District Court / NCLT / SAT
- Apply court-specific formatting requirements
- Select pleading type:
- Plaint / Written Statement / Counter-Claim / Interlocutory Application / Writ
- Legal research on applicable law (legal-research-agent)
- Build evidence chronology (chronology-builder-agent)
- Draft the pleading with mandatory disclaimer
- Analyse opposing arguments and suggest responses
Generates litigation-[YYYYMMDD-HHMM].docx + .html
HITL Gate 1 — litigation plan approval HITL Gate 2 — draft pleading approval (ABSOLUTE STOP — never auto-approve) HITL Gate 3 — opposing analysis approval
Usage:
/litigate labour dispute — ₹8.5L claim, Pune labour court, 3 witnesses
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.
- 8d ago First seen · 33 lines · 11 tokens per session scan A 43e64f1d02d0
litigate is a command published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 287 once invoked, about $0.0001 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
open-agreements
Help the user fill a standard legal agreement template and produce a DOCX file.
wiki-ingest
Ingest a local file into the wiki knowledge base.
wiki-tune
Tune wiki schema and conventions interactively.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
vlm-ocr
Run the vlm-ocr skill on the task below. It has three phases: evaluate (compare candidate OCR systems against stratified human ground truth and pick one on measured CER/WER), run (build and execute the production VLM-OCR pipeline — model selection, image handling, prompts, architecture, batching, accuracy evaluation…