extract

extract is a command for Claude Code from ishwarjha/legalant. It costs 10 tokens per session (203 once invoked), scanned A, original, MIT.

A document-data extraction command that collects specified facts from several files and puts them into a comparison table. It can work with legal information such as parties, dates, contract duties, and risk terms.

In plain words
What is it for?
Use it to extract fields from a document set, identify missing or conflicting entries, and produce a table with page references for review.
Why use it?
It removes the need to read multiple documents side by side and manually compare each requested detail.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents.

Part of the legalant plugin — 4 skills, 16 commands, 18 agents shipped together

Good fit Use it to extract fields from a document set, identify missing or conflicting entries, and produce a table with page references for review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ishwarjha/legalant/extract
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ishwarjha/legalant

Made for: Claude Code.

Or install legalant, the plugin that ships this one along with the rest of its 4 skills, 16 commands, 18 agents.

Wrote 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.

agentmods badge for extract

README.md
[![agentmods](https://agentmods.dev/badge/commands/ishwarjha/legalant/extract.svg)](https://agentmods.dev/commands/ishwarjha/legalant/extract)
Your own site
<a href="https://agentmods.dev/commands/ishwarjha/legalant/extract"><img src="https://agentmods.dev/badge/commands/ishwarjha/legalant/extract.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 203 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00203
Opus 5 $0.00005 $0.00102
Sonnet 5 $0.00002 $0.00041
Haiku 4.5 $0.00001 $0.00020

Measured 8d ago against content hash c3c8cc4381f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

extract 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 8d 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.

legalant/commands/extract.md · 22 lines

What it actually says

Invoke the document-table-agent sub-agent to extract and tabulate data from documents.

Documents and fields to extract:

$ARGUMENTS

The agent will:

  1. Parse all specified documents
  2. Extract the requested data fields (or auto-detect key fields if not specified)
  3. Build a structured comparison table with: Document | Clause | Extracted Value | Page Reference
  4. Flag missing fields, conflicting values, or blank entries
  5. Support extraction types: financial terms, dates, parties, covenants, conditions precedent, risk allocations
  6. Generate extract-[YYYYMMDD-HHMM].docx with extraction table + .html

HITL Gate fires before delivery — respond with APPROVED or REVISE: [add fields / correct values].

Usage: /extract all VDR documents — extract: parties, governing law, arbitration seat, liability cap

Changes

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.

  1. 8d ago First seen · 22 lines · 10 tokens per session scan A c3c8cc4381f8

Subscribe to this mod's changes

extract is a command published in the GitHub repository ishwarjha/legalant (6 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 203 once invoked, about $0.0001 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.