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 agentmods add skills/magic3007/dotfiles/clinical-reportsnpx skills add magic3007/dotfiles --skill clinical-reportsgit clone --depth 1 https://github.com/magic3007/dotfilesWrote 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/magic3007/dotfiles/clinical-reports)<a href="https://agentmods.dev/skills/magic3007/dotfiles/clinical-reports"><img src="https://agentmods.dev/badge/skills/magic3007/dotfiles/clinical-reports.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.08541 |
| Opus 5 | $0.00036 | $0.04270 |
| Sonnet 5 | $0.00014 | $0.01708 |
| Haiku 4.5 | $0.00007 | $0.00854 |
Grade A, and why
clinical-reports 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 4d 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
98% identical to clinical-reports — 10 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 — 1,133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Report Writing
Overview
Clinical report writing is the process of documenting medical information with precision, accuracy, and compliance with regulatory standards. This skill covers four major categories of clinical reports: case reports for journal publication, diagnostic reports for clinical practice, clinical trial reports for regulatory submission, and patient documentation for medical records. Apply this skill for healthcare documentation, research dissemination, and regulatory compliance.
Critical Principle: Clinical reports must be accurate, complete, objective, and compliant with applicable regulations (HIPAA, FDA, ICH-GCP). Patient privacy and data integrity are paramount. All clinical documentation must support evidence-based decision-making and meet professional standards.
When to Use This Skill
This skill should be used when:
- Writing clinical case reports for journal submission (CARE guidelines)
- Creating diagnostic reports (radiology, pathology, laboratory)
- Documenting clinical trial data and adverse events
- Preparing clinical study reports (CSR) for regulatory submission
- Writing patient progress notes, SOAP notes, and clinical summaries
- Drafting discharge summaries, H&P documents, or consultation notes
- Ensuring HIPAA compliance and proper de-identification
- Validating clinical documentation for completeness and accuracy
- Preparing serious adverse event (SAE) reports
- Creating data safety monitoring board (DSMB) reports
Visual Enhancement with Scientific Schematics
⚠️ MANDATORY: Every clinical report MUST include at least 1 AI-generated figure using the scientific-schematics skill.
This is not optional. Clinical reports benefit greatly from visual elements. Before finalizing any document:
- Generate at minimum ONE schematic or diagram (e.g., patient timeline, diagnostic algorithm, or treatment workflow)
- For case reports: include clinical progression timeline
- For trial reports: include CONSORT flow diagram
What ships with it
31 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.
- assets/case_report_template.md 9.5 KB
- assets/clinical_trial_csr_template.md 9.0 KB
- assets/clinical_trial_sae_template.md 10 KB
- assets/consult_note_template.md 7.2 KB
- assets/discharge_summary_template.md 12 KB
- assets/hipaa_compliance_checklist.md 12 KB
- assets/history_physical_template.md 9.0 KB
- assets/lab_report_template.md 8.3 KB
- assets/pathology_report_template.md 6.5 KB
- assets/quality_checklist.md 9.7 KB
- assets/radiology_report_template.md 7.8 KB
- assets/soap_note_template.md 7.1 KB
- references/case_report_guidelines.md 18 KB
- references/clinical_trial_reporting.md 20 KB
- references/data_presentation.md 21 KB
- references/diagnostic_reports_standards.md 18 KB
- references/medical_terminology.md 15 KB
- references/patient_documentation.md 21 KB
- references/peer_review_standards.md 15 KB
- references/README.md 8.4 KB
- references/regulatory_compliance.md 17 KB
- scripts/check_deidentification.py 10 KB runs code
- scripts/compliance_checker.py 2.1 KB runs code
- scripts/extract_clinical_data.py 2.6 KB runs code
- scripts/format_adverse_events.py 3.0 KB runs code
- scripts/generate_report_template.py 4.6 KB runs code
- scripts/generate_schematic_ai.py 32 KB runs code
- scripts/generate_schematic.py 5.0 KB runs code
- scripts/terminology_validator.py 4.0 KB runs code
- scripts/validate_case_report.py 11 KB runs code
- scripts/validate_trial_report.py 2.8 KB runs code
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.
- 4d ago First seen · 1,133 lines · 71 tokens per session scan A 7c4b85fdc918
clinical-reports is a skill published in the GitHub repository magic3007/dotfiles (11 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 8,541 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to clinical-reports, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
git-commit
Create a new git commit for staged changes. Use when the user asks to commit staged changes with an auto-generated Conventional Commits message, or when Claude Code itself wants to run git commit.
github-pr-create
Create a pull request with an auto-generated description. Use when the user asks to open a PR for the current branch's changes.
inspect-malicious-code
Inspect a project for potentially malicious code (malware, spyware, etc.) using static analysis only. Use when the user asks to audit a project or dependency for malicious or suspicious code.
verify-git-command-location
Verify that the correct git binary is in use, especially when running under WSL with a Windows filesystem. Use the first time a git command is executed in a session.
git-add
Stage files for commit after scanning for secrets. Use when the user asks to stage files with git add.
git-verify-identity
Verify that git user.name and user.email are configured. Use automatically before any git operation that requires identity (commits, rebases, cherry-picks, etc.), and when the user asks to check or verify their git identity.