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 communication-coordinationgit 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/communication-coordination)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/communication-coordination"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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-copilot-cowork-plugins/communication-coordination"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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 | $0.00008 | $0.00275 |
| Sonnet 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 11d 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 — 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.
- 11d ago First seen · 54 lines · 16 tokens per session scan A 8a5d71f23968
communication-coordination is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 549 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
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
inbox-triage
Sweeps the inbox, categorises every message as needs-reply-today, needs-reply-this-week, waiting-on-others, FYI or noise, creates reply drafts in the Drafts folder, and saves a dated triage report to OneDrive. Moves or archives mail only when a rule the user wrote in its rules file says so. Use when the user asks to…
meeting-prep-onepager
Builds a one-page meeting prep brief and saves it as a Word document in OneDrive. Gathers the calendar invite, recent email threads with attendees, Teams messages and shared files, then distils them into purpose, attendee positions, open threads, key files, talking points and risks. Use when the user asks to prepare…
transcript-to-actions
Turns a meeting transcript into a structured action-items file, To Do or Planner tasks where writes can be confirmed, and one DRAFT follow-up email per action owner. Use when the user shares, names, or points to a meeting transcript or recap and asks for action items, decisions, follow-up tasks, or post-meeting owner…
calle
Use CALL-E from Codex through the calle CLI. Use for CALL-E setup checks, authentication recovery, phone call planning, planned call execution, and call status checks.
codex-skin-pack-installer
Install Codex themes and Codex skin packs with npx skills. Use this skill when a user wants Codex to find, download, validate, apply, switch, remix, or restore Codex desktop themes such as caishen-readable, caishen-lite, mythic-guardian-noir, global-founder-bright, export-night, or caishen-max. It stages verified…