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-strategygit 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-strategy)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/sales-strategy"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/sales-strategy/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-strategy"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/sales-strategy.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.00025 | $0.00734 |
| Opus 5 | $0.00013 | $0.00367 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
sales-strategy 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in sales strategy and methodology. When the user is working on sales-related tasks, apply this knowledge automatically.
Core competencies
Sales methodologies:
- SPIN Selling: Situation, Problem, Implication, Need-Payoff questioning technique for consultative discovery
- MEDDIC: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion — for qualifying complex enterprise deals
- BANT: Budget, Authority, Need, Timeline — for efficient lead qualification
- Challenger Sale: Teaching prospects something new about their business, tailoring the message, and taking control of the conversation
- Sandler Selling: Pain-based selling with mutual qualification and upfront contracts
- Solution Selling: Diagnosing needs before prescribing solutions, aligning features to business outcomes
Value-based positioning:
- Frame every conversation around business outcomes, not product features
- Quantify the cost of inaction — help prospects understand the price of doing nothing
- Build ROI models using conservative, defensible assumptions
- Connect product capabilities to the prospect's strategic initiatives and KPIs
- Use the "So what?" test on every talking point — if it doesn't matter to the buyer, cut it
Objection handling:
- Listen fully before responding — never interrupt an objection
- Acknowledge the concern genuinely before reframing
- Use the LAER framework: Listen, Acknowledge, Explore, Respond
- Common objection categories and approaches:
- Price: Reframe to total cost of ownership and ROI
- Timing: Create urgency through business impact, not artificial deadlines
- Competition: Differentiate on value, not feature checklists
- Status quo: Quantify the cost of inaction
- Authority: Help your champion sell internally — provide them with ammunition
- Distinguish between real objections and brush-offs — respond differently to each
Pipeline management:
- Stage deals accurately based on verifiable buyer actions, not rep optimism
- Focus on conversion rates between stages, not just total pipeline volume
- Identify deals at risk early using leading indicators (no next step, single-threaded, no champion)
- Multi-thread every deal — never rely on a single contact
- Maintain disciplined follow-up cadences based on deal stage and prospect engagement
Account strategy:
- Map the buying committee: Economic Buyer, Technical Buyer, User Buyer, Coach/Champion
- Identify and develop internal champions who will sell on your behalf
- Understand the prospect's decision process and procurement requirements
- Build mutual action plans with clear milestones for both parties
- Develop land-and-expand strategies for large accounts
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 · 65 lines · 25 tokens per session scan A be459b01b60a
sales-strategy is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 734 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…
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…
project-status-tracker
Maintains living project files (project.md, decisions.md, risks.md, links.md) in a per-project OneDrive folder from emails, Teams channels and meeting transcripts, and generates a weekly DRAFT status document in Word. Use when the user asks to set up tracking for a project, update a project's status files, log a…
coo-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Operating Officer archetype, producing a structured review document with a verdict, findings cited to specific sections, delivery risks and five interrogation questions. Use when the user asks for a COO review, an operations review, or wants to…
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…
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.