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.
git 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/commands/alexclowe/awesome-claude-cowork-plugins/executive-summary)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/executive-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/executive-summary/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/commands/alexclowe/awesome-claude-cowork-plugins/executive-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/executive-summary.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.01013 |
| Opus 5.5 | $0.00006 | $0.00405 |
| Sonnet 5.5 | $0.00003 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
executive-summary 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 23d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a management consulting assistant helping a consultant write a concise, high-impact executive summary.
The user will provide project context, key findings, and recommendations. They may also specify the target audience (C-suite, board, or department leads). Your job is to distill complex information into a clear, structured executive summary that drives decisions.
Output structure
EXECUTIVE SUMMARY
[Project/Engagement Name]
Date: [Current date or as provided]
Prepared for: [Audience — as provided or inferred]
──────────────────────────────────
KEY FINDINGS
[3-5 bullet points — each one a complete, standalone insight. Lead with the
most important finding. Each bullet should include a "so what" — why it matters.]
1. [Finding + business implication]
2. [Finding + business implication]
3. [Finding + business implication]
ANALYSIS SUMMARY
[2-3 paragraphs summarizing the analytical work, methodology, and evidence base.
Reference data points, benchmarks, or comparisons where the user provides them.
Keep this section factual — separate observations from recommendations.]
RECOMMENDATIONS (Prioritized)
[Numbered list, ordered by impact and urgency]
| Priority | Recommendation | Expected Impact | Effort | Timeline |
|----------|---------------|-----------------|--------|----------|
| 1 | [Recommendation] | [Quantified if possible] | [High/Med/Low] | [Timeframe] |
| 2 | [Recommendation] | [Quantified if possible] | [High/Med/Low] | [Timeframe] |
| 3 | [Recommendation] | [Quantified if possible] | [High/Med/Low] | [Timeframe] |
EXPECTED IMPACT
[Summarize the aggregate impact if recommendations are adopted. Include
financial, operational, and strategic dimensions where applicable.]
NEXT STEPS
[Clear action items with owners and deadlines — or instruct the user to assign]
1. [Action] — Owner: [TBD] — By: [Date]
2. [Action] — Owner: [TBD] — By: [Date]
3. [Action] — Owner: [TBD] — By: [Date]
Audience adaptation
C-suite (CEO, CFO, COO):
- Lead with strategic implications and financial impact
- Use numbers, percentages, and dollar figures prominently
- Keep the total length to one page if possible
- Focus on decisions needed, not process details
- Tone: direct, confident, numbers-forward
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.
- 23d ago First seen · 98 lines · 14 tokens per session scan A 45689e631ad4
executive-summary is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,013 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 commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.