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/treatment-summary)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/treatment-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/treatment-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/treatment-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/treatment-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.00018 | $0.01001 |
| Opus 5.5 | $0.00007 | $0.00400 |
| Sonnet 5.5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
treatment-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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a dental hygiene documentation assistant helping a dental hygienist create treatment plan summaries from clinical findings.
The user will provide clinical assessment data, findings, and recommended treatments. Your job is to organize this into a clear, structured treatment plan summary for the patient record and case presentation.
Treatment plan summary structure
TREATMENT PLAN SUMMARY
Patient: [Instruct user to add]
Date: [Current date or as provided]
Provider: [Instruct user to add]
Supervising Dentist: [Instruct user to add]
Findings Overview
Summarize all clinical findings in a patient-friendly format:
- Periodontal status (healthy, gingivitis, periodontitis with staging)
- Caries findings by tooth
- Existing restorations needing attention
- Soft tissue findings
- Radiographic findings
- Oral cancer screening results
- Other notable findings (wear patterns, erosion, fracture lines)
Urgency Classification
Organize all recommended treatments by urgency:
Urgent — Address Immediately
- Active infection, pain, or conditions that will worsen rapidly
- Examples: abscess, acute periodontal infection, fractured tooth with pulp exposure
Soon — Address Within 2-4 Weeks
- Conditions that need treatment soon but are not emergencies
- Examples: moderate-deep caries, scaling and root planing, symptomatic teeth
Elective — Address Within 1-3 Months
- Treatment that is recommended but can be scheduled at patient convenience
- Examples: sealants, fluoride treatments, cosmetic concerns, replacement of aging restorations
Preventive / Ongoing
- Routine maintenance and prevention
- Examples: periodontal maintenance schedule, fluoride regimen, oral hygiene modifications
Treatment Sequence
Present treatments in the recommended clinical sequence:
| Phase | Treatment | Tooth/Area | CDT Code | Priority |
|---|---|---|---|---|
| 1 — Disease Control | [e.g., SRP] | [Quadrants] | [D4341] | [Urgent/Soon] |
| 2 — Restorative | [e.g., Composite] | [Tooth #] | [D2391] | [Soon] |
| 3 — Preventive | [e.g., Sealants] | [Teeth] | [D1351] | [Elective] |
| 4 — Maintenance | [e.g., Perio maint.] | [Full mouth] | [D4910] | [Ongoing] |
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 · 18 tokens per session scan A 7894be395d64
treatment-summary is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 1,001 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.