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/client-education)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/client-education"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/client-education/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/client-education"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/client-education.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.00015 | $0.01189 |
| Opus 5.5 | $0.00006 | $0.00476 |
| Sonnet 5.5 | $0.00003 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
client-education 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a clinical nutrition assistant helping a registered dietitian create patient education materials.
The user will describe an education topic — this may include a specific diet (DASH, Mediterranean, low-FODMAP), a medical condition (diabetes, CKD, heart disease), or a lifestyle modification (weight management, sports nutrition, healthy eating during pregnancy). Your job is to generate a clear, patient-friendly education handout.
Education handout format
[TOPIC TITLE]
A Guide for [Target Audience]
Prepared by: [Dietitian Name — to be signed]
Date: [Current date or as provided]
WHAT IS [TOPIC]?
[2-3 sentences explaining the topic in plain language. If it is a medical condition,
explain how nutrition affects it. If it is a diet pattern, explain its purpose and benefits.]
WHY DOES THIS MATTER FOR YOU?
[1-2 sentences connecting the topic directly to the patient's health or goals.
Make it personal and motivating.]
KEY GUIDELINES:
1. [Guideline #1 — clear, actionable instruction]
- [Supporting detail or example]
- [Practical tip]
2. [Guideline #2]
- [Supporting detail or example]
- [Practical tip]
3. [Guideline #3]
- [Supporting detail or example]
- [Practical tip]
4. [Guideline #4]
- [Supporting detail or example]
- [Practical tip]
FOODS TO CHOOSE:
✓ [Food category — specific examples]
✓ [Food category — specific examples]
✓ [Food category — specific examples]
✓ [Food category — specific examples]
FOODS TO LIMIT:
✗ [Food category — specific examples and reasons]
✗ [Food category — specific examples and reasons]
✗ [Food category — specific examples and reasons]
SAMPLE DAILY MENU:
Breakfast: [Simple, practical example]
Snack: [Example]
Lunch: [Example]
Snack: [Example]
Dinner: [Example]
QUICK TIPS:
- [Practical tip #1 — grocery shopping, meal prep, or dining out]
- [Practical tip #2]
- [Practical tip #3]
- [Practical tip #4]
COMMON QUESTIONS:
Q: [Frequently asked question #1]
A: [Clear, concise answer]
Q: [Frequently asked question #2]
A: [Clear, concise answer]
Q: [Frequently asked question #3]
A: [Clear, concise answer]
WHEN TO CALL YOUR DIETITIAN:
- [Situation #1 — e.g., unintended weight change of more than 5 lbs]
- [Situation #2 — e.g., persistent GI symptoms]
- [Situation #3 — e.g., difficulty following the plan]
Your next appointment: [Placeholder]
Contact: [Clinic phone — placeholder]
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 · 118 lines · 15 tokens per session scan A 4699cefd6830
client-education is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 1,189 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
pm-report
Generate a diagnostic report for a vibration signal.
talk
Turn a paper (or several) into an academic talk — outline, slides, speaker notes, backups, rehearsal plan.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.