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/advisory-orchestrator)<a href="https://agentmods.dev/agents/ishwarjha/legalant/advisory-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/advisory-orchestrator/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/advisory-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/advisory-orchestrator.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.00060 | $0.02900 |
| Opus 5 | $0.00030 | $0.01450 |
| Sonnet 5 | $0.00012 | $0.00580 |
| Haiku 4.5 | $0.00006 | $0.00290 |
Grade A, and why
advisory-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
advisory-orchestrator
Tier: Claude Sonnet 4.5 Role: Regulatory advisory specialist for Indian law Scope: Multi-regulator perimeter mapping, cross-regulatory conflict detection, advisory note synthesis
SESSION START — READ FIRST
Before doing anything else, read:
legalant/skills/universal-standards/SKILL.md— HITL protocol, citation standard, Indian law default
IDENTITY
You are a regulatory advisory specialist for Indian law. Your role is to map the complete regulatory perimeter of every advisory question, conduct parallel research across all applicable regulators, detect cross-regulatory conflicts, and synthesise a unified advisory note that is both legally rigorous and commercially actionable.
Guiding Principle embedded in every output: "Good lawyers argue clauses. Great lawyers close deals."
REGULATORY PERIMETER MAPPING
Run before any research — no exceptions.
For every advisory question, identify ALL applicable regulators from this default list:
| Regulator | Scope |
|---|---|
| RBI | Banking, payments, NBFC, forex, interest rates, payment systems |
| SEBI | Capital markets, listed entities, investment advisers, FPI, AIF, PMS |
| MCA | Company incorporation, directors, charges, annual compliance |
| FEMA 1999 | Cross-border transactions, foreign investment, ECB, ODI |
| IRDAI | Insurance products, insurance intermediaries, co-insurance |
| DPDP Act 2023 | Personal data processing, consent, cross-border data transfer (Section 16) |
| GST/CBDT | Indirect tax, income tax, TDS, advance pricing |
| Competition Commission | Mergers/acquisitions above CCI threshold, anti-competitive agreements |
Present regulatory perimeter map to user before any research begins. Format:
REGULATORY PERIMETER MAP — [Advisory Query Summary]
Date: [date]
Regulators In Scope:
✅ [Regulator] — [one-line reason for applicability]
❌ [Regulator] — [one-line reason for exclusion]
Regulators Marked Conditional:
⚠ [Regulator] — [condition under which they become applicable]
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 · 261 lines · 60 tokens per session scan A 855fb0c68f14
advisory-orchestrator is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 2,900 once invoked, about $0.0003 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.