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 sales-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/sales-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/sales-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/sales-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/sales-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/sales-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.00799 |
| Opus 5 | $0.00009 | $0.00400 |
| Sonnet 5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
sales-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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to craft effective sales communications. When the user is preparing outreach emails, follow-ups, proposals, or client-facing materials, apply these principles automatically.
Persuasive writing principles
Structure for impact:
- Lead with the prospect's problem or goal, not your product
- Use the "AIDA" framework: Attention, Interest, Desire, Action
- Front-load value — the most important point goes in the first sentence
- One idea per paragraph, one CTA per email
- End every communication with a clear, specific next step
Personalization at scale:
- Reference something specific to the prospect: their company, role, recent news, or shared context
- Mirror the prospect's language — if they say "revenue growth," don't say "top-line expansion"
- Adapt tone to the audience:
- C-suite: Strategic, concise, outcome-focused. Respect their time.
- VP/Director: Balance of strategy and tactical detail. Show you understand their metrics.
- Manager/Individual Contributor: Tactical, detailed, focused on day-to-day impact.
- Avoid generic phrases that signal a mass email: "I hope this finds you well," "I wanted to reach out," "Just circling back"
Urgency without pressure:
- Use legitimate business reasons for urgency: fiscal year timelines, implementation lead times, market conditions
- Never use false scarcity or manipulative tactics
- Frame urgency around the prospect's timeline, not yours: "To hit your Q3 launch target, we'd need to start onboarding by..."
- Create FOMO through social proof: "Teams like [similar company] saw results within 60 days"
- Respect "not now" — it's different from "not interested"
Email best practices
Subject lines:
- Keep under 50 characters when possible
- Be specific and relevant to the prospect
- Use lowercase for a more personal feel in cold outreach
- Test patterns: question, stat, name-drop, insight, direct ask
- Never use ALL CAPS, excessive punctuation, or clickbait
Body copy:
- Keep cold emails under 125 words
- Keep follow-ups under 100 words
- Use short paragraphs (1-3 sentences max)
- Write at an 8th-grade reading level — clarity beats sophistication
- Use "you" more than "we" — ratio of 2:1 minimum
- Bold or bullet key points for scanners
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 · 72 lines · 18 tokens per session scan A aebaae19938d
sales-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 799 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
commitment-catcher
Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with…
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…
project-dashboard-builder
Generates a self-contained single-file HTML project dashboard (status banner, milestones, risks heat list, decisions log, links) from the tracker files in /Documents/Cowork/projects/, saved as dashboard- -YYYY-MM-DD.html. Use when the user asks for a project dashboard, a shareable or pinnable status page, an HTML…
chro-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Human Resources Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, people and organisation risks and five interrogation questions. Use when the user asks for a CHRO or HR review, a…
customer-advocate-reviewer
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, then saves a structured review document with a verdict, findings that cite the artifact, customer-side risks and five interrogation questions. Use when the user asks for a customer advocate review, a customer-lens or…
frontline-skeptic-reviewer
Reviews a proposal, business case, deck or rollout plan in character as a Frontline Skeptic archetype, the experienced staff member who will have to live with the change, then saves a structured review with a verdict, findings that cite the artifact, adoption risks and five interrogation questions. Use when the user…