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 client-communicationgit 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/client-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/client-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-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-claude-cowork-plugins/client-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-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.5 | $0.00007 | $0.00441 |
| Sonnet 5.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 1mo 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:
- client-communication — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 99 lines · 18 tokens per session scan A a37290e068e3
client-communication is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (31 stars, last pushed 15d ago), licensed MIT. It adds 18 tokens to every session and 1,103 once invoked, about $0.0001 per session on Opus 5.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
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…
hipaa-compliance
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any…
ccpa
California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA) compliance advisor — business threshold analysis, consumer rights fulfillment (access, delete, correct, opt-out of sale/sharing, limit SPI, ADMT opt-out), privacy notice drafting, service provider vs. contractor vs. third-party…
eu-ai-act
EU AI Act (Regulation (EU) 2024/1689) compliance advisor — risk classification across all four tiers, all 9 prohibited practices (Art. 5, including the nudification/CSAM prohibition from Dec 2, 2026), all 8 Annex III high-risk use case areas, provider and deployer obligations (Arts. 9–17, 26), GPAI model obligations…
cmmc
Expert CMMC 2.0 (Cybersecurity Maturity Model Certification) advisor for US defense contractors and subcontractors in the Defense Industrial Base (DIB). Use this skill whenever a user asks about CMMC 2.0, CMMC Level 1, Level 2, or Level 3, DoD cybersecurity compliance, NIST SP 800-171, CUI (Controlled Unclassified…