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-claude-cowork-plugins --skill patient-educationgit 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/skills/alexclowe/awesome-claude-cowork-plugins/patient-education)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/patient-education"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/patient-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/skills/alexclowe/awesome-claude-cowork-plugins/patient-education"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/patient-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.00019 | $0.01141 |
| Opus 5.5 | $0.00008 | $0.00456 |
| Sonnet 5.5 | $0.00004 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
patient-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- patient-education — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to communicate health information to patients effectively across diverse literacy levels. When the user is preparing patient-facing materials, education handouts, or discharge instructions, apply these principles automatically.
Health literacy adaptation
Health literacy is the ability to find, understand, and use health information to make decisions. Nearly 9 out of 10 adults have difficulty using everyday health information. When creating patient education materials:
Reading level guidelines:
- General patient education: 5th-6th grade reading level
- Consent forms and legal documents: as simple as possible with required legal language
- Medication instructions: 4th-5th grade reading level
- Use readability assessment tools (Flesch-Kincaid, SMOG) to verify reading level
Plain language principles:
- Use short sentences (15 words or fewer)
- Use common, everyday words:
- "take" not "administer"
- "swelling" not "edema"
- "high blood sugar" not "hyperglycemia"
- "belly" not "abdomen"
- "blood thinner" not "anticoagulant" (but include the medical term parenthetically)
- Use active voice: "Take your medicine every morning" not "Medicine should be taken daily"
- Use "you" and "your" to speak directly to the patient
- Define medical terms when they must be used
- Avoid acronyms — or spell them out on first use
Document design:
- Use headers and subheaders to organize information
- Use bulleted or numbered lists instead of dense paragraphs
- Use white space generously — crowded pages reduce comprehension
- Bold key actions and important warnings
- Use at least 12-point font for printed materials
- Use high contrast (black text on white background)
- Include visuals, diagrams, or illustrations when they add clarity
- Limit each handout to 2-3 key messages — information overload reduces retention
Teach-back method
The teach-back method is the gold standard for verifying patient understanding. Guide nurses in using it:
- Explain the information clearly using plain language
- Assess understanding by asking the patient to explain it back:
- "I want to make sure I explained this clearly. Can you tell me in your own words how you'll take this medication?"
- "If your daughter asked you what the doctor said today, what would you tell her?"
- "Can you show me how you would check your blood sugar?"
- Clarify if the patient cannot teach it back — re-explain using different words or methods
- Reassess until the patient demonstrates understanding
- Document that teach-back was used and the patient's comprehension level
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 · 107 lines · 19 tokens per session scan A 605533c27beb
patient-education is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 1,141 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 skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
algo-sensei
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
career-path-planner
Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.
onboarding-guide-creator
New hire onboarding guide generation with role-specific content, structured timelines, and resource organization. Use when creating employee onboarding materials, welcome guides, or training documentation.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
learning-gap-analyzer
Map understanding, identify knowledge gaps, and build targeted learning plans with spaced repetition. Use when assessing knowledge levels, designing study plans, or optimizing learning paths.