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 client-communicationgit 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/client-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/client-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/client-communication/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/client-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/client-communication.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.01103 |
| Opus 5 | $0.00009 | $0.00551 |
| Sonnet 5 | $0.00004 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
client-communication 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 client-communication — 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to communicate legal information to clients effectively. When the user is preparing client-facing materials, correspondence, or explanations, apply these principles automatically.
Plain-language legal explanations
Most clients are not lawyers. When drafting client-facing communications:
- Explain legal concepts in everyday language first, then provide the legal term: "The other side can ask for documents and information from us — this is called 'discovery'"
- Avoid unnecessary Latin: use "for this reason" not "ergo," "among other things" not "inter alia," "in itself" not "per se" (unless the term has specific legal significance)
- Use analogies and examples to explain complex concepts: "A deposition is like testifying in court, but it happens in a conference room instead of a courtroom"
- Break complex procedures into numbered steps: "Here's what will happen next: 1. We file the complaint. 2. The other side has 30 days to respond..."
- Translate legal jargon in contracts: "This clause means that if they break the contract, the most they would ever have to pay you is $50,000 — no matter how much you actually lost"
- When presenting options, clearly explain the pros, cons, and likely outcomes of each
- Use concrete dollar amounts and timelines when possible — "This could take 12-18 months" is more helpful than "This may take some time"
Client correspondence standards
Status update letters/emails:
- Lead with the most important information or action item
- Summarize where the case stands in 1-2 sentences
- Explain what has happened since the last communication
- State what will happen next and when
- Identify any action items for the client (with deadlines)
- Invite questions
- Keep it concise — most clients do not need a legal treatise
Advice letters:
- State the question presented clearly
- Provide a brief answer upfront before the detailed analysis
- Explain the law in accessible terms
- Apply the law to the client's specific facts
- Present your recommendation clearly, including the reasoning
- Note uncertainties or risks honestly
- Identify next steps and decision points
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 · 99 lines · 18 tokens per session scan A a37290e068e3
client-communication 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 1,103 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 client-communication, 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.