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 client-deliverablesgit 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/client-deliverables)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/client-deliverables"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/client-deliverables/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/client-deliverables"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/client-deliverables.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.00014 | $0.00717 |
| Opus 5 | $0.00007 | $0.00358 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
client-deliverables 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to create high-quality client-facing consulting deliverables. When the user is preparing proposals, presentations, reports, or other client-facing materials, apply these principles automatically.
Document principles
Lead with the answer (pyramid principle):
- Every document, section, and slide should start with the key takeaway
- The reader should be able to stop at any point and have received the most important information up to that point
- Supporting evidence follows the conclusion, not the other way around
Visual hierarchy and structure:
- Use clear, descriptive headings — a reader should be able to scan headings alone and understand the narrative
- Consistent formatting throughout — heading levels, bullet styles, table formats
- White space is a feature, not wasted space — dense pages lose the reader
- Number sections and pages for easy reference in discussions
Quantify impact:
- Translate findings into business terms: revenue, cost, time, risk, market share
- Use specific numbers over vague qualifiers ("$4.2M opportunity" not "significant opportunity")
- Show the math — include assumptions behind projections so readers can assess credibility
- Use ranges when precision is uncertain (e.g., "$3-5M in annual savings")
Content discipline:
- Make every slide and page earn its place — if it does not advance the argument, cut it
- Separate "what we found" (facts) from "what we recommend" (opinions) with clear labels
- Include "so what" for every data point — raw data without interpretation is not a deliverable
- Anticipate the reader's questions and answer them proactively
Presentation norms
Follow standard top-tier consulting presentation conventions:
Slide structure:
- Action title at the top — a complete sentence stating the slide's key message
- Body supports the action title with evidence (charts, tables, bullet points)
- Source line at the bottom citing data sources
- Takeaway box or callout for the critical "so what"
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 · 67 lines · 14 tokens per session scan A 27e9c6367990
client-deliverables is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 717 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…
report-attachment-analyzer
Tracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for…
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…
sharepoint-review-sweeper
Sweeps a configured SharePoint library for documents past their review date, builds a dated reminder spreadsheet (document, owner, due date, days overdue, link) and drafts one notification email per document owner, as Drafts only, never sent. Use when the user asks to find overdue document reviews, run a review sweep…
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…
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…