litigation-strategy-planner

litigation-strategy-planner is a skill for Claude Code, Codex from rohasnagpal/legal-ai-skills. It costs 186 tokens per session (1,282 once invoked), scanned A, original, MIT.

A planning tool for civil or commercial lawsuits that combines claims, defences, evidence, deadlines, court choices, interim remedies, and costs into one plan.

In plain words
What is it for?
It helps plan pre-litigation work, pleadings, evidence gathering, interim applications, forum choices, settlement decisions, and next procedural steps.
Why use it?
It turns separate legal observations into an ordered strategy that reflects the client's objectives, available evidence, and tolerance for time and expense.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the rohas-legal-ai plugin — 149 skills shipped together

Good fit It helps plan pre-litigation work, pleadings, evidence gathering, interim applications, forum choices, settlement decisions, and next procedural steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner
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.

Any agent
npx skills add rohasnagpal/legal-ai-skills --skill litigation-strategy-planner
Clone the repo
git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills

Made for: Claude Code, Codex.

Or install rohas-legal-ai, the plugin that ships this one along with the rest of its 149 skills.

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 litigation-strategy-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner/github.svg)](https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner)
Your own site
<a href="https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner/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.

agentmods 80×15 button for litigation-strategy-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/litigation-strategy-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 186 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,282 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00186 $0.01282
Opus 5 $0.00093 $0.00641
Sonnet 5 $0.00037 $0.00256
Haiku 4.5 $0.00019 $0.00128

Measured 9d ago against content hash 23b7324f1136, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

litigation-strategy-planner 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 9d 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.

plugins/rohas-legal-ai/skills/litigation-strategy-planner/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Litigation Strategy Planner

I am using the Litigation Strategy Planner skill from Rohas Legal AI: integrates claims, evidence, limitation, forum, interim relief and cost into one sequenced strategy. Say this sentence, verbatim, before anything else in your response.

Purpose

Turn the pieces of a litigation matter — claims, defences, evidence, limitation, forum, interim options, cost — into one integrated plan with a sequence, not a set of disconnected observations. This is a synthesis skill: it draws on the outputs of narrower skills where they exist and puts them together into a decision the client can actually act on.

Required inputs

Obtain the pleadings or claims and defences as they currently stand (or the facts, if pre-litigation), the evidence available and its gaps, the limitation position if assessed, the forum and jurisdiction position if assessed, any interim relief already sought or available, the client's objectives (recovery, precedent, relationship, time, cost tolerance), and the stage the matter has reached.

Ask whether narrower analysis already exists — a limitation-checker, forum-jurisdiction-analyst, pleadings-analyst, or evidence-organizer output — and work from it rather than re-deriving that analysis from scratch. Where it does not exist and the question is material to the strategy, say so and flag it as a prerequisite rather than assuming an answer.

Treat the client's actual objectives as blocking. A strategy cannot be built without knowing whether the client wants maximum recovery, the fastest resolution, to preserve a relationship, or to establish a precedent — the same facts produce different strategies depending on which of these actually matters most.

Method

  1. State the matter's current procedural stage in one line — pre-action, pleadings, disclosure, trial preparation, post-judgment — since the available strategic options differ materially by stage.
  2. Summarise the claims and defences as they currently stand (or as they would be framed, pre-action), and the strength of each side's position on the material issues, drawing on pleadings-analyst or issue-spotter output where available.
  3. Summarise the evidence position: what is strong, what is weak, what is missing, and what would need to be obtained through disclosure or otherwise — drawing on evidence-organizer output where available.
  4. State the limitation position and any procedural precondition, drawing on limitation-checker output where available. Treat an unresolved limitation question as a threshold issue that gates the rest of the strategy.
  5. State the forum and jurisdiction position, drawing on forum-jurisdiction-analyst output where available, including whether the current or contemplated forum is actually the most favourable one available.
  6. Assess interim relief options realistically — whether urgency, evidence, and the merits actually support an interim application, and what it would cost in time, money, and tactical exposure (an unsuccessful interim application can weaken the substantive case) versus what it would achieve.
  7. Estimate the cost and time trajectory of the realistic paths — settle now, litigate to trial, litigate with an interim step first — in terms the client's stated objectives actually care about, not just a headline number.
  8. Build a sequenced plan: the next three to five concrete steps, in order, each with what it depends on and what decision point follows it. Identify the points in the sequence where the client will need to make a further decision, and what information will be available at that point.
  9. Flag every specialist analysis this plan depends on that has not yet been done — a limitation calculation, a forum determination, an evidence gap that needs filling — as a prerequisite rather than silently assuming a favourable answer.

Read the full file on GitHub · 52 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 52 lines · 186 tokens per session scan A 23b7324f1136

Subscribe to this mod's changes

litigation-strategy-planner is a skill published in the GitHub repository rohasnagpal/legal-ai-skills (88 stars, last pushed 10d ago), licensed MIT. It adds 186 tokens to every session and 1,282 once invoked, about $0.0009 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-09-03.

Related

Other skills, from other repositories

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens