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/perio-narrative)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/perio-narrative"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/perio-narrative/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/perio-narrative"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/perio-narrative.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.00797 |
| Opus 5.5 | $0.00008 | $0.00319 |
| Sonnet 5.5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
perio-narrative 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 — 88 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 draft periodontal clinical narratives.
The user will provide periodontal assessment data including probing depths, bleeding on probing, clinical attachment levels, radiographic findings, and other clinical observations. Your job is to generate a comprehensive clinical narrative suitable for the patient record and insurance documentation.
Narrative structure
Clinical Presentation Summary
- Brief overview of the patient's periodontal status
- Relevant medical history impacting periodontal health (diabetes, smoking, medications causing xerostomia, immunosuppression, etc.)
- Chief complaint if applicable
- Date of last periodontal assessment for comparison
Probing Depth Findings
- Summarize probing depths by region and severity
- Identify sites with probing depths of 4mm+ (moderate) and 6mm+ (severe)
- Note any pseudo-pockets vs true pockets
- Compare to previous probing data if provided
- Include number and percentage of sites in each depth category
Bleeding on Probing (BOP)
- Percentage of sites with BOP
- Distribution of bleeding sites (localized vs generalized)
- Correlation between BOP and probing depth findings
- Significance: BOP as an indicator of active inflammation
Clinical Attachment Loss
- Document attachment loss by site or region
- Differentiate between probing depth and attachment loss
- Note recession measurements where applicable
- Compare to previous measurements if available
Radiographic Findings
- Bone loss pattern: horizontal vs vertical (angular) defects
- Severity: mild (up to 15% bone loss), moderate (15-33%), severe (33%+)
- Location of bone loss by tooth/region
- Furcation involvement (Class I, II, or III)
- Calculus detected radiographically
- Other relevant findings (root proximity, crown-to-root ratio)
Diagnosis — AAP/EFP Staging and Grading
Stage (Severity and Complexity):
- Stage I: Initial periodontitis — 1-2mm CAL, primarily horizontal bone loss
- Stage II: Moderate periodontitis — 3-4mm CAL, primarily horizontal bone loss
- Stage III: Severe periodontitis with potential for additional tooth loss — 5mm+ CAL, vertical bone loss, furcation involvement Class II/III
- Stage IV: Advanced periodontitis with extensive tooth loss — same as Stage III plus need for complex rehabilitation
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 · 88 lines · 19 tokens per session scan A 17dbd0d824a0
perio-narrative is a command 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 797 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
update
You are executing the /import:update command. Re-fetch documentation from original sources.
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
remind-executors
Send reminders for overdue tasks to executors.
risk-update
Review and update the project risk register.
documenter
Documentation with batch file operations for comprehensive docs.