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/review)<a href="https://agentmods.dev/commands/ishwarjha/legalant/review"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/review/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/review"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/review.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.00160 |
| Opus 5 | $0.00004 | $0.00080 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
review 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.
What it actually says
Invoke the document-review-agent sub-agent to review and analyse the specified document.
Document or context to review:
$ARGUMENTS
The agent will:
- Read the document from the VDR or path specified
- Apply the CONTRACT mnemonic checklist (8-point review)
- Produce an issues table with severity ratings (High / Medium / Low)
- Flag any DPDP Act 2023, FEMA, or SEBI compliance gaps
- Generate review-[YYYYMMDD-HHMM].docx + .html
HITL Gate fires before finalising the review output.
Usage:
/review path/to/document.pdfor/review SHA Clause 8.2 — liability cap
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 · 21 lines · 8 tokens per session scan A 5479840eef1a
review 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 160 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
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
dashboard
Build a shareable HTML dashboard of your hunt — funnel, status, categories, recruiter scores — from the tracker.
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.
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.