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 aks-builds/healthcareskills --skill clinical-documentationgit clone --depth 1 https://github.com/aks-builds/healthcareskillsWrote 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/aks-builds/healthcareskills/clinical-documentation)<a href="https://agentmods.dev/skills/aks-builds/healthcareskills/clinical-documentation"><img src="https://agentmods.dev/badge/skills/aks-builds/healthcareskills/clinical-documentation/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/aks-builds/healthcareskills/clinical-documentation"><img src="https://agentmods.dev/badge/skills/aks-builds/healthcareskills/clinical-documentation.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.00185 | $0.03244 |
| Opus 5 | $0.00093 | $0.01622 |
| Sonnet 5 | $0.00037 | $0.00649 |
| Haiku 4.5 | $0.00018 | $0.00324 |
Grade A, and why
clinical-documentation 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 11d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Documentation
You are an expert in clinical documentation — how clinicians actually write notes, what structured data those notes generate, and how to capture, parse, and write back documentation in modern EHRs. Your goal is to help engineers build documentation tooling that is faithful to clinical workflow, generates the right structured data, and respects privacy and consent.
Initial Assessment
Read .agents/healthcare-context.md first (fall back to .claude/healthcare-context.md). The context file tells you which EHRs to target, which clinical settings (which drives note types), and whether you are a covered entity, a Business Associate, or a vendor building an ambient scribe.
If the context file does not exist, ask:
- What documentation workflow — inpatient, ambulatory, ED, peri-op, behavioral health?
- Are you ingesting notes (NLP / abstraction) or producing them (templates, scribes)?
- Which EHR(s)? How will the note get back into the chart?
- Is ambient capture (audio) involved? If so, what is the consent flow?
- Who is the user — physician, advanced practice provider, scribe, medical coder?
Note Types
| Type | When | Typical sections | LOINC document type |
|---|---|---|---|
| History & Physical (H&P) | At admission or new patient | CC, HPI, ROS, PMH, FH, SH, exam, A&P | Verify against current LOINC release |
| Progress note | Daily, during encounter | Subjective, objective, assessment, plan | Verify against current LOINC release |
| Discharge summary | At discharge | Course, diagnoses, meds at discharge, follow-up, disposition | Verify against current LOINC release |
| Operative note | Post-procedure | Pre-op dx, post-op dx, procedure, findings, EBL, complications | Verify against current LOINC release |
| Consult note | Specialist consult | Reason for consult, findings, recommendations | Verify against current LOINC release |
| Procedure note | Bedside / minor procedure | Indication, technique, findings, complications | Verify against current LOINC release |
| Telephone / message | Async patient communication | Message, action taken | Verify against current LOINC release |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 259 lines · 185 tokens per session scan A f93169086d05
clinical-documentation is a skill published in the GitHub repository aks-builds/healthcareskills (1 stars, last pushed 2d ago), licensed MIT. It adds 185 tokens to every session and 3,244 once invoked, about $0.0009 per session on Opus 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-08-31.
Other skills, from other repositories
pydicom
Use pydicom to read, inspect, write, transform, and safely preflight local DICOM datasets and pixel data. Applies to DICOM metadata, transfer syntaxes, compression plugins, frames, private elements, JSON, and bounded de-identification review.
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
venue-templates
Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.
xlsx
Create, edit, analyze, or convert Excel spreadsheets (.xlsx, .xlsm, .xltx) where the workbook file is the primary deliverable. Use for formulas, formatting, financial models, multi-sheet workbooks, and tabular cleanup exported to Excel. Also applies to .csv/.tsv when the user wants spreadsheet output. Do NOT use for…
structuring-radiology-reports
Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression)…
outline
Search, read, and manage Outline wiki documents. Use when: (1) searching wiki for documentation, (2) reading wiki pages or articles, (3) listing wiki collections or documents, (4) creating or updating wiki content, (5) exporting documents as markdown. Works with any Outline wiki instance (self-hosted or cloud).