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-copilot-cowork-plugins --skill litigation-workflowgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-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-copilot-cowork-plugins/litigation-workflow)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/litigation-workflow"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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-copilot-cowork-plugins/litigation-workflow"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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 10d 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.
This is a copy
100% identical to litigation-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 10d ago First seen · 129 lines · 24 tokens per session scan A a4450def9018
litigation-workflow is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 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. It is 100% identical to litigation-workflow, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
general-counsel-reviewer
Reviews a proposal, business case, deck or plan in character as a General Counsel archetype, then saves a structured review document with a verdict, findings that cite the artifact, legal risks and five interrogation questions. Use when the user asks for a legal review, a general counsel pressure-test of a document…
works-council-reviewer
Reviews a proposal, business case, deck or rollout plan in character as a Works Council Representative archetype, then saves a structured review document with a verdict, findings that cite the artifact, employee-impact risks and five interrogation questions. Use when the user asks for a works council review, an…
personal-data-protection
Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP 27/2022, Thailand PDPA B.E. 2562 (2019), Malaysia PDPA 2010 (with the 2024 Amendments), or Philippines DPA (RA 10173). Use when reviewing or modifying code that touches personal data …
eu-ai-act-readiness
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency, high-risk controls, general-purpose AI obligations, governance, and implementation milestones. Use when an organization…
compliance-checklist-generation
Build evidence-oriented readiness checklists for frameworks such as SOC 2, HIPAA, PCI DSS, and GDPR, with gaps and remediation priorities. Use when the user needs an internal readiness assessment or control-mapping plan; do not use it to certify compliance or replace an auditor or counsel.
contract-review
Analyze contracts for risks, obligations, key clauses, and generate structured risk reports with severity ratings. Use when the user requests contract review or provides relevant inputs for this workflow.