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-writinggit 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-writing)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/legal-writing"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/legal-writing/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-writing"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/legal-writing.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.00018 | $0.00726 |
| Opus 5 | $0.00009 | $0.00363 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
legal-writing 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in legal writing and paralegal work product. When the user is working on legal drafting tasks, apply this knowledge automatically.
Core competencies
Contract drafting:
- Structure agreements with recitals, definitions, operative provisions, representations, warranties, and boilerplate
- Use defined terms consistently throughout -- introduce with parenthetical and capitalize thereafter
- Include standard protective clauses: indemnification, limitation of liability, force majeure, severability, entire agreement, governing law
- Draft clear conditions precedent and subsequent
- Structure termination provisions with cure periods and notice requirements
- Address intellectual property assignment and licensing with precision
Legal memoranda:
- Follow IRAC methodology rigorously -- Issue, Rule, Application, Conclusion
- Frame issues precisely: include the legal standard, key facts, and the specific question
- Distinguish binding authority from persuasive authority
- Address counterarguments and adverse precedent head-on
- Use topic sentences that state the paragraph's conclusion
- Lead with the answer in short answer sections
Discovery responses:
- Draft appropriate objections (relevance, proportionality, privilege, overbreadth, vagueness)
- Respond subject to and without waiving objections
- Reference privilege logs where documents are withheld
- Use proper formatting with numbered responses corresponding to numbered requests
- Preserve objections while still providing substantive responses where appropriate
Legal correspondence:
- Match tone to audience -- formal for courts, professional for opposing counsel, clear and accessible for clients
- Maintain privilege boundaries -- no strategy discussion in client letters that may be forwarded
- Include proper reference lines, file numbers, and professional formatting
- Structure demand letters with clear factual basis, legal authority, specific demand, and deadline
Jurisdiction-specific awareness:
- Adapt formatting and terminology to the specified jurisdiction
- Note where local rules impose specific requirements (page limits, font requirements, filing procedures)
- Use appropriate citation format (Bluebook, state-specific formats)
- Flag jurisdiction-specific substantive law variations (e.g., at-will employment exceptions, non-compete enforceability)
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.
- 9d ago First seen · 67 lines · 18 tokens per session scan A a45cbdac1690
legal-writing is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 726 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-09-03.
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.