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 wolfenazz/YzPzCode --skill clinical-case-reportgit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/clinical-case-report)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/clinical-case-report"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/clinical-case-report/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/wolfenazz/yzpzcode/clinical-case-report"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/clinical-case-report.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.00073 | $0.02030 |
| Opus 5.5 | $0.00029 | $0.00812 |
| Sonnet 5.5 | $0.00015 | $0.00406 |
| Haiku 4.5 | $0.00007 | $0.00203 |
Grade A, and why
clinical-case-report 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 1mo 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.
This is a copy
100% identical to clinical-case-report — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Case Report Skill
Generate a structured medical case presentation for clinical rounds, conferences, or documentation. The output follows standard medical formatting conventions used in hospital settings worldwide.
What you will produce
A single-page HTML case report (index.html). Content varies by format
(see references/case-formats.md — selected in Step 0):
SOAP / Conference format:
- Patient identification — age, sex, chief complaint
- History of Present Illness (HPI) — chronological narrative with pertinent positives and negatives
- Past Medical History, Medications, Allergies
- Review of Systems
- Physical Examination — systematic findings by system
- Vital Signs — formatted table with reference ranges and flags
- Investigations — laboratory results and imaging findings
- Assessment — primary diagnosis and differential (3–5 items) with clinical reasoning for each
- Management Plan — evidence-based, organised by problem
Brief Rounds format (daily review, ward round, handover, ICU, post-call):
- ID line — age, sex, day of admission, primary problem
- Interval events / current status — what has changed since last review
- Active problems — numbered list
- Plan-by-problem — concise actions for each active problem
- Full HPI and systematic physical examination are not included
Step-by-step workflow
Step 0 — Load reference files
Before starting, read both reference files:
references/case-formats.md— use this to choose the correct output format (SOAP, Conference, or Brief Rounds) based on the user's contextreferences/checklist.md— keep P0 gates in mind throughout; you must pass all P0 items before emitting the final artifact
Step 1 — Parse the brief
Read the user's prompt and extract:
- Patient age and sex
- Chief complaint or presenting problem
- Any vitals, labs, or imaging the user has provided
- Clinical context: ED, ward rounds, conference case, outpatient, etc.
- Specialty context: cardiology, emergency, internal medicine, etc.
What ships with it
4 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.
- 1mo ago First seen · 209 lines · 73 tokens per session scan A 997d0745f61c
clinical-case-report is a skill published in the GitHub repository wolfenazz/YzPzCode (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 73 tokens to every session and 2,030 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to clinical-case-report, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
figures
Makes publication-quality plots from data with matplotlib, learning curves, scaling laws, benchmark and ablation comparisons, Pareto trade-offs, heatmaps and confusion matrices, sized for the page, vector, with uncertainty shown. Use whenever results are plotted, charted or visualized for a paper, report or answer, or…
agdoc
Generate a context-aware HTML document and show it in an agterm overlay, end to end. With no arguments it works out the subject from the session - the issue, PR, branch, plan, diff or topic being discussed - and asks with the likely variants when that is unclear; with arguments it takes them as the brief, including…
epd-parser
Extract GWP, life-cycle stages, certifications, and impact metrics from an EPD PDF. Use when given a declaration to parse; not to find or compare EPDs.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
latex
Compile one specified LaTeX document, resolve build errors, audit citations, and report build quality. Use when a .tex source must be built or a concrete compilation failure repaired. Not for corpus-wide build checks, visual polish after a clean build, or creating a project; use $latex-health-check, $latex-polish, or…
bib-parse
Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.