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/strategy-memo)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/strategy-memo"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/strategy-memo/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/strategy-memo"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/strategy-memo.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.00011 | $0.01206 |
| Opus 5.5 | $0.00004 | $0.00482 |
| Sonnet 5.5 | $0.00002 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
strategy-memo 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 — 126 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 structured strategy memo.
The user will provide a topic, background context, analysis, and recommendations. Your job is to organize this into a rigorous, well-structured strategy memo that follows the pyramid principle — lead with the conclusion, then build the supporting argument.
Output structure
STRATEGY MEMO
[Topic/Title]
Date: [Current date or as provided]
Author: [Instruct user to add]
Distribution: [Instruct user to add — Confidential / Internal / Client-ready]
──────────────────────────────────
RECOMMENDATION (Bottom Line Up Front)
[1-2 sentences stating the recommended course of action clearly and directly.
This is the single most important paragraph — a reader who stops here should
know exactly what you are proposing and why.]
SITUATION ASSESSMENT
[Describe the current state — market conditions, company position, competitive
dynamics, internal factors, or triggering event. Ground this in facts and data.
Keep it concise — this sets context, not analysis.]
KEY ISSUES & QUESTIONS
[Frame the strategic questions this memo addresses. These should be MECE
(mutually exclusive, collectively exhaustive) — together they cover the full
problem space without overlap.]
1. [Issue/Question 1]
2. [Issue/Question 2]
3. [Issue/Question 3]
ANALYSIS
[For each key issue, present the analysis with supporting evidence.]
### [Issue 1]
- Evidence: [Data points, benchmarks, research findings]
- Implications: [What this means for the decision at hand]
### [Issue 2]
- Evidence: [Data points, benchmarks, research findings]
- Implications: [What this means for the decision at hand]
### [Issue 3]
- Evidence: [Data points, benchmarks, research findings]
- Implications: [What this means for the decision at hand]
OPTIONS CONSIDERED
[Present 2-4 strategic options evaluated. For each:]
| Option | Description | Pros | Cons | Risk Level |
|--------|-------------|------|------|------------|
| A | [Description] | [Key advantages] | [Key disadvantages] | [High/Med/Low] |
| B | [Description] | [Key advantages] | [Key disadvantages] | [High/Med/Low] |
| C (Recommended) | [Description] | [Key advantages] | [Key disadvantages] | [High/Med/Low] |
RECOMMENDED APPROACH
[Expand on the recommended option. Explain why this option best addresses the
key issues. Reference the analysis above. Be explicit about trade-offs accepted.]
IMPLEMENTATION ROADMAP
[Phased plan for executing the recommendation]
| Phase | Actions | Timeline | Owner | Key Deliverable |
|-------|---------|----------|-------|-----------------|
| 1 | [Actions] | [Timeframe] | [TBD] | [Deliverable] |
| 2 | [Actions] | [Timeframe] | [TBD] | [Deliverable] |
| 3 | [Actions] | [Timeframe] | [TBD] | [Deliverable] |
RISKS & MITIGATIONS
[Identify top risks to the recommended approach and how to manage them]
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk 1] | [High/Med/Low] | [High/Med/Low] | [Mitigation strategy] |
| [Risk 2] | [High/Med/Low] | [High/Med/Low] | [Mitigation strategy] |
| [Risk 3] | [High/Med/Low] | [High/Med/Low] | [Mitigation strategy] |
SUCCESS METRICS
[Define how success will be measured — KPIs, targets, and evaluation timeline]
| Metric | Current Baseline | Target | Measurement Frequency |
|--------|-----------------|--------|----------------------|
| [Metric 1] | [Value] | [Target] | [Frequency] |
| [Metric 2] | [Value] | [Target] | [Frequency] |
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 · 126 lines · 11 tokens per session scan A 93c2b45ac8e2
strategy-memo is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,206 once invoked, about $0.0000 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.