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 communication-coordinationgit 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/communication-coordination)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/communication-coordination"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/communication-coordination/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/communication-coordination"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/communication-coordination.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.00016 | $0.00549 |
| Opus 5.5 | $0.00006 | $0.00220 |
| Sonnet 5.5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
communication-coordination 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 22d 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:
- communication-coordination — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Communication & Coordination
Email Management
- Triage inbox into categories: urgent/action-required, FYI, delegatable, archive
- Draft responses that match the executive's voice, tone, and level of formality
- Use templates for recurring communication types (scheduling, acknowledgments, declines)
- Flag emails that have been waiting for a response beyond 24-48 hours
- Summarize long email threads into key points, decisions, and open questions
- Manage distribution lists and ensure the right stakeholders are included
Professional Writing
- Match tone to audience: formal for board/external, conversational for internal teams
- Lead with the key message or ask in the first sentence
- Keep emails concise — aim for 5 sentences or fewer when possible
- Use bullet points for multiple items, action items, or decisions
- Proofread for grammar, tone, and unintended implications before sending
- Include clear subject lines that indicate urgency and topic
Follow-Up Systems
- Maintain a follow-up tracker with owner, deadline, and status for every open item
- Send reminders 24-48 hours before deadlines
- Escalate overdue items with context rather than just a nudge
- Close the loop: confirm receipt of deliverables and acknowledge completion
- Use recurring check-in cadences for long-running projects
- Document follow-up outcomes for future reference
Meeting Recaps and Action Items
- Send meeting summaries within 2 hours of the meeting ending
- Structure recaps as: decisions made, action items (owner + deadline), open questions
- Distinguish between FYI attendees and action owners
- Track action item completion across meetings and flag carryovers
- Use consistent formatting so recipients can scan quickly
- Archive recaps in a shared location for reference
Stakeholder Communication
- Maintain a stakeholder map with communication preferences and frequency
- Tailor updates to each audience: executives want outcomes, teams want details
- Proactively communicate schedule changes, delays, or blockers
- Coordinate cross-functional communication to prevent duplicate or conflicting messages
- Draft talking points for executive presentations and all-hands meetings
- Manage RSVPs, attendee lists, and event communications
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.
- 22d ago First seen · 54 lines · 16 tokens per session scan A 8a5d71f23968
communication-coordination is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 549 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-09-24.
Other skills, from other repositories
coordinate-meeting
Coordinates project meetings: generates a structured agenda, creates a Google Calendar event, and prepares a protocol template. Covers 5 meeting types across the full project lifecycle — tasks #6, #15, #17, #20, #26. Meeting types: Go/No-Go (Phase 1, #6), Client Demo (Phase 3, #15), Sprint Planning (Phase 4, #17)…
generate-change-impact
Generates a change impact assessment file (change-impact-CR-001.xlsx) for Phase 4 — Development. PM describes a scope change request; the agent classifies the change (scope / budget / timeline / resource), analyzes impact on project-plan.md and project-budget.xlsx, calculates timeline delta, budget delta, and risk…
generate-estimate
Generates a preliminary timeline and budget estimate for an IT project (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, constraints, team list), applies analogy-based estimation using built-in agent knowledge of typical IT projects, and produces a three-scenario (optimistic…
generate-approval-letter
Generates an approval-letter.md email body and an email-tpl-approval.md template for Phase 2 — Planning. Reads project-plan.md, project-budget.xlsx, and resource-plan.md to compose a formal approval request addressed to all Approver-level stakeholders from stakeholder-map.md. Produces two artifacts: the letter email…
generate-budget
Generates a detailed project budget (project-budget.xlsx) for Phase 2 — Planning, based on preliminary-estimate.xlsx and resource-plan.md. Produces a single baseline scenario structured by project phases and cost categories (team, infrastructure, GTM), with a contingency reserve as a separate line item. Covers task #9…
generate-questionnaire
A questionnaire builder for IT projects. It creates either a client questionnaire for gathering requirements at the start or a lessons-learned questionnaire for the team at the end, and can organize the answers.