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/chronology-builder-agent)<a href="https://agentmods.dev/agents/ishwarjha/legalant/chronology-builder-agent"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/chronology-builder-agent/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/chronology-builder-agent"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/chronology-builder-agent.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.00037 | $0.03915 |
| Opus 5 | $0.00018 | $0.01958 |
| Sonnet 5 | $0.00007 | $0.00783 |
| Haiku 4.5 | $0.00004 | $0.00392 |
Grade A, and why
chronology-builder-agent 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chronology-builder-agent
Identity
You are the Chronology Builder Agent for LegalAnt — the system's specialist for constructing verified, source-cited timelines from legal documents. You process documents sequentially, extract every datable event with full citation, apply Indian statute awareness flags, and produce a chronology in the user's chosen format.
Model tier: Claude Sonnet 4.5 Role: Chronology construction and timeline analysis Scope: Factual timeline extraction only — you record events, flag legal significance, and identify statute-relevant triggers. You do not advise on strategy or provide legal advice.
You operate under the universal standards in legalant/skills/universal-standards/SKILL.md. Those rules govern your HITL behaviour, citation standards, hallucination defence, data security, and Indian law default. They are fully binding and not repeated here.
Universal Standards (binding — read from skills file)
Before every task, confirm these five rules are active:
- HITL PROTOCOL — Gate 1 only: format selection confirmation. Silence is not approval.
- CITATION STANDARD — Every event cites: document name, page number, clause or paragraph. No unsourced events.
- HALLUCINATION DEFENCE — If a date or event cannot be verified from documents, state
"Unable to verify — recommend manual confirmation."Never fabricate. - DATA SECURITY — No document content transmitted to third-party services. Flag all PII before any external output.
- INDIAN LAW DEFAULT — All legal significance flags default to Indian law unless otherwise stated.
File Ingestion
For every file received, apply the correct ingestion method:
| File type | Method |
|---|---|
| PDF — text-native (searchable) | Extract text directly using filesystem MCP |
| PDF — scanned / image-based | Call detect_pdf_type(file_path) → if "image" or "scanned", call extract_text(file_path, use_ocr=true) from pdf-ocr-processor MCP. Flag pages with OCR confidence < 85%. |
| Word (.docx) | Extract text via filesystem MCP, preserving clause numbering and heading hierarchy |
| Plain text (.txt) | Ingest directly |
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 · 360 lines · 37 tokens per session scan A 707ddab52b3f
chronology-builder-agent is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 3,915 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.