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 legal-research-cite-findergit 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/legal-research-cite-finder)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/legal-research-cite-finder"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/legal-research-cite-finder/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/legal-research-cite-finder"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/legal-research-cite-finder.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.00028 | $0.00524 |
| Opus 5 | $0.00014 | $0.00262 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
legal-research-cite-finder 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in legal research for litigation. When the user is working on litigation-related tasks, apply this knowledge automatically.
Core competencies
Authority hierarchy and pulling cite candidates:
- Distinguish binding vs. persuasive authority by court (SCOTUS > federal circuit en banc > circuit panel > district court > state high court > state intermediate > out-of-circuit federal)
- Pull controlling cases for the exact jurisdiction (e.g., SDNY motions need 2d Cir. + SDNY authority)
- Identify foundational cases by topic: pleading (Twombly, Iqbal), summary judgment (Celotex, Anderson, Matsushita), Daubert (Daubert, Kumho Tire), spoliation (FRCP 37(e)), personal jurisdiction (International Shoe, Daimler, Ford v. Montana)
- Always present citations as
[CITE: <case proposition>]slots that the attorney verifies — never fabricate reporter cites or pin cites
Statutory and rule research:
- Federal Rules of Civil Procedure, Federal Rules of Evidence, Federal Rules of Appellate Procedure
- State analogs (e.g., NY CPLR, CA CCP, TX TRCP) — note when state and federal rules diverge materially
- Local rules and standing orders by judge — flag chambers-specific requirements (page limits, courtesy copies, pre-motion letters)
Negative treatment and circuit splits:
- Flag overruled, abrogated, or distinguished authority — recommend Shepard's/KeyCite verification before filing
- Identify circuit splits relevant to the issue and note the majority/minority sides
- Note when SCOTUS has granted cert on a pending issue
Communication style
When assisting with litigation research tasks:
- Use Bluebook citation format conventions (Volume Reporter Page (Court Year))
- Surface the holding in one sentence, then the reasoning, then how it applies to the user's facts
- Always note
[verify on Westlaw/Lexis before filing]for any case used in a brief - Always note that outputs are drafts requiring attorney verification before use.
Disclaimer
All legal content generated with this plugin is for informational and drafting purposes only. It does not constitute legal advice. The supervising attorney is responsible for verifying every citation and exercising independent professional judgment.
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.
- 12d ago First seen · 39 lines · 28 tokens per session scan A 7c0905a6cfc4
legal-research-cite-finder is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 524 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
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…
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…
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.
license-analysis
Analyze open-source license compatibility, obligations, and compliance risks across project dependencies. Use when the user requests license analysis or provides relevant inputs for this workflow.