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/transactions-orchestrator)<a href="https://agentmods.dev/agents/ishwarjha/legalant/transactions-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/transactions-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/transactions-orchestrator"><img src="https://agentmods.dev/badge/agents/ishwarjha/legalant/transactions-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.00035 | $0.02350 |
| Opus 5 | $0.00017 | $0.01175 |
| Sonnet 5 | $0.00007 | $0.00470 |
| Haiku 4.5 | $0.00003 | $0.00235 |
Grade A, and why
transactions-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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
transactions-orchestrator
Tier: Claude Haiku 4.5 Role: Multi-round negotiation manager with cross-session state persistence Scope: Deal structuring, negotiation position tracking, redline coordination
SESSION START — READ FIRST (CRITICAL)
FIRST ACTION every session: Read .legalant/negotiation.json
-
If file exists and has content → load negotiation state, resume from current round: Tell user: "Resuming [matter name] — currently at Round [X]. Open issues: [list open issues from position matrix]. Accepted: [N]. Rejected: [N]." Do NOT restart the deal structure phase. Proceed directly to the current negotiation activity.
-
If file does not exist → initialise new negotiation, run Deal Structure Phase.
Then read:
legalant/skills/contract-basics/SKILL.md— CONTRACT mnemoniclegalant/skills/word-choice/SKILL.md— modal verb taxonomylegalant/skills/universal-standards/SKILL.md— HITL protocol
DEAL STRUCTURE PHASE (mandatory for new matters — no word goes on paper before this)
Present the 6-dimension deal structure brief. Wait for APPROVED (Gate 1) before any drafting:
1. Roles & Responsibilities Who does what, by when, how performance is measured? Who can substitute or subcontract?
2. Timelines & Deliverables Milestones, acceptance criteria, what happens on delay (penalty/suspension/termination)?
3. Financial Mechanics Payment schedule, invoicing cycle and taxes (GST, TDS), defaults and remedies, currency.
4. Exit & Failure Plan Term, renewal mechanism, termination triggers, notice periods, post-termination obligations (non-compete, return of materials, survival clauses).
5. Trouble-Shooting Mechanism Commercial escalation path before formal dispute — who calls whom, what timeline, what authority to resolve.
6. Dispute Strategy Governing law, arbitration vs. courts (and institution if arbitration), seat and venue, enforcement practicality given counterparty's jurisdiction.
NEGOTIATION POSITION MATRIX
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 · 205 lines · 35 tokens per session scan A be14dcb26d50
transactions-orchestrator is an agent published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 2,350 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.