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.
npx skills add alexclowe/awesome-claude-cowork-plugins --skill litigation-workflowgit clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/skills/alexclowe/awesome-claude-cowork-plugins/litigation-workflow)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/litigation-workflow"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/litigation-workflow/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/skills/alexclowe/awesome-claude-cowork-plugins/litigation-workflow"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/litigation-workflow.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.00024 | $0.01512 |
| Opus 5 | $0.00012 | $0.00756 |
| Sonnet 5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
litigation-workflow 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- litigation-workflow — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in civil litigation workflow and the Federal Rules of Evidence. When the user is working on a litigation matter — case management, deposition preparation, evidence handling, motion practice, trial prep — apply this knowledge automatically.
Case management
Pleading stage:
- Complaint drafting standards under Twombly / Iqbal plausibility — facts, not legal conclusions
- Affirmative defenses must be pled in the answer or risk waiver (Rule 8(c))
- Counterclaims and cross-claims — compulsory vs permissive
- Rule 12 motions: timing, consolidation, waiver of unraised defenses
Scheduling and case management orders:
- Rule 16 conference and Rule 26(f) report
- Discovery cutoff, expert disclosure deadlines, dispositive motion deadlines, pretrial conference, trial date
- Modification requires good cause; calendar conflicts must be raised promptly
Discovery management:
- Rule 26(a) initial disclosures — names of likely witnesses, document categories, computation of damages, insurance
- Rule 26(b)(1) proportionality — scope of discovery is governed by relevance and proportionality
- Rule 26(b)(5) privilege log requirements
- Rule 34 RFP responses — specificity required, no boilerplate objections (sanctions risk)
- ESI: Rule 34 production format, search terms, custodian negotiations, predictive coding/TAR
- Rule 30(b)(6) corporate depositions — designating witness binds the entity
- Meet-and-confer obligations under Rule 37 before motion to compel
Deposition preparation
For taking a deposition:
- Outline organized by topic, not by document — keep the witness from anticipating
- Mark exhibits in advance with clean copies
- 30(b)(6) topics: serve early, get firm designations, prepare for objections to scope
- Lock in admissions before introducing impeaching documents
- Reserve time for cleanup at the end — confirm what the witness has not seen, has not relied on, does not know
For defending a deposition:
- Witness prep: review documents, prior statements, deposition notice topics
- Form objections (leading, compound, vague, mischaracterizes testimony) preserve the record
- Substantive objections (relevance, etc.) typically reserved for trial under Rule 32
- Privilege instructions: stop testimony, state privilege on the record, take a break
- Errata sheet: limited corrections only — substantive changes invite cross-examination
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 · 129 lines · 24 tokens per session scan A a4450def9018
litigation-workflow is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,512 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-30.
Other skills, from other repositories
property-management
Property management expertise including fair housing law, lease administration, HOA governance, and vendor management.
integration-management
Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A…
portfolio
Track the UK IP portfolio — registrations, renewals, maintenance fees (UK IPO annual fees, EUIPO renewals, EPO annuities, Madrid Monitor). Use when checking what's renewing, adding or updating an asset, recording a filing, or auditing the register for gaps, lapses, and post-Brexit coverage issues. Receives handoffs…
launch-review
Full UK launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo. UK regulatory…
demand-intake
Pre-drafting context gathering for a Letter Before Action or Letter of Claim — parties, facts, basis, leverage, BATNA, and privilege filters — written to a structured intake.md the demand-draft skill reads. Use when the user wants to prep a Letter Before Action, run intake before drafting, or capture context for a…
legal-hold
Issue, refresh, release, or report on preservation notices — drafts the notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a preservation notice", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.