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/chronology)<a href="https://agentmods.dev/commands/ishwarjha/legalant/chronology"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/chronology/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/chronology"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/chronology.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.00008 | $0.00194 |
| Opus 5 | $0.00004 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
chronology 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 11d 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 chronology-builder-agent sub-agent to extract and build a chronological timeline.
Documents or context:
$ARGUMENTS
The agent will:
- Parse all specified documents for dated events (explicit and implied dates)
- Extract: agreements signed, notices served, deadlines triggered, breaches alleged, payments made
- Order events chronologically with source citations (document + page + clause)
- Flag ambiguous dates or sequence conflicts
- Identify limitation period implications (Limitation Act 1963)
- Generate chronology-[YYYYMMDD-HHMM].docx with timeline table + .html
HITL Gate fires before delivering the timeline — respond with APPROVED or REVISE: [add/remove events].
Usage:
/chronology all documents in vdr/or/chronology SHA_v1.txt labour_notice.pdf
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.
- 11d ago First seen · 22 lines · 8 tokens per session scan A 3c371f36fafc
chronology is a command published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 194 once invoked, about $0.0000 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).
sync
Upload past Claude Code sessions to Beezi analytics, skipping ones already uploaded.
telemetry
Turn Beezi plugin crash reporting on or off, with or without account correlation.