lawsuit-analysis

lawsuit-analysis is a command for Claude Code from llamadrive/bengo-toolkit. It costs 24 tokens per session (468 once invoked), scanned A, original, MIT.

A command that analyses legal case documents and produces a structured, self-contained HTML report. It can organise people, claims, responses, evidence, and events from documents such as complaints or briefs.

In plain words
What is it for?
Reviewing lawsuit documents, building timelines, mapping claims to evidence, identifying participants, and generating a printable case report.
Why use it?
It reduces the manual work of sorting information across legal filings. The resulting HTML file can be opened directly and printed to PDF, while an audit log records the analysis.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is Read, Write, Glob, mcp__docx-editor__read_document, mcp__agent-format__render_agent_file, Bash(python3 skills/_lib/audit.py:*), Bash(python3 skills/_lib/workspa.

Part of the bengo-toolkit plugin — 15 skills, 25 commands, 3 MCP servers shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add llamadrive/bengo-toolkit
Claude Code
/plugin install bengo-toolkit

Made for: Claude Code.

Or install bengo-toolkit, the plugin that ships this one along with the rest of its 15 skills, 25 commands, 3 MCP servers.

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 lawsuit-analysis

README.md
[![agentmods](https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/lawsuit-analysis.svg)](https://agentmods.dev/commands/llamadrive/bengo-toolkit/lawsuit-analysis)
Your own site
<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/lawsuit-analysis"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/lawsuit-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 468 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00024 $0.00468
Opus 5 $0.00012 $0.00234
Sonnet 5 $0.00005 $0.00094
Haiku 4.5 $0.00002 $0.00047

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

Security

Grade A, and why

lawsuit-analysis 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 6d 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.

commands/lawsuit-analysis.md · 26 lines

What it actually says

訴訟関連文書(訴状、答弁書、準備書面、証拠説明書等)を読み取り、構造化データ(タイムライン、登場人物、主張・認否・証拠)を抽出して自己完結 HTML(ダブルクリックで開け、⌘P で PDF 化できる単一ファイル)を生成する。 MCP Apps 対応環境(Claude Desktop, Cursor 等)では併せてインライン描画も行う。 監査ログは現在の案件フォルダの ./.claude-bengo/audit.jsonl に記録される。 ./.claude-bengo/ がまだ無ければ、実行時に現在のフォルダへ自動作成される。

$ARGUMENTS: 文書ファイルのパスまたはディレクトリ(任意。なければ対話で確認)。

Step 0: 動作環境ガード

Bash: python3 skills/_lib/workspace.py check --require local_fs --require docx_mcp
  • exit 0 → 次の Step へ進む
  • exit 2 → stdout の日本語メッセージをそのままユーザーへ表示して停止
  • exit 1 → stderr の error JSON をユーザーに伝えて停止

Step 1

まず skills/lawsuit-analysis/SKILL.md を Read ツールで読み込み、そこに記載された手順に従って実行する。

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. 6d ago First seen · 26 lines · 24 tokens per session scan A ed7988c1ce0c

Subscribe to this mod's changes

lawsuit-analysis is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 468 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.