Borrowing it
Nothing to install: this file belongs to aizech/clinical-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aizech/clinical-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/aizech/clinical-skillsWrote 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/instructions/aizech/clinical-skills/claude-md)<a href="https://agentmods.dev/instructions/aizech/clinical-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/aizech/clinical-skills/claude-md.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.1 | $0.01675 | $0.01675 |
| Opus 5 | $0.00838 | $0.00838 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
clinical-skills CLAUDE.md 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 7d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Skills - Contributing Guide
Welcome to Clinical Skills
Thank you for contributing to Clinical Skills! This repository provides AI agent skills for medical imaging and healthcare workflows, developed by Corpus Analytica.
Purpose
Clinical Skills provides specialized knowledge for AI agents working in healthcare and radiology contexts:
- Radiology workflow automation - PACS queries, report analysis
- Clinical documentation - Structured reporting, patient communication
- AI integration - Detection pipelines, LLM assistance
- Quality assurance - Metrics, audits, compliance
- Research support - Literature search, dataset management
Contribution Philosophy
We welcome contributions that:
- Follow Test-Driven Development (TDD) principles
- Include evals.json for skill validation
- Benefit radiology AI broadly
- Maintain high quality standards
Before Opening a PR
Please complete these steps before submitting:
- Search first - Check existing issues and PRs (open and closed)
- One change per PR - Each PR should address one skill or improvement
- Test locally - Run validation scripts before submitting
- Skills:
./scripts/validate-skills.sh - CLI tools:
pytest tools/clis/tests/ -v
- Skills:
- Human review - Ensure a human has reviewed your changes
- Clear description - Explain what problem this solves
What Makes a Great Contribution
Skill Changes
- Start with evals - Write test cases in
evals/evals.jsonfirst - Keep SKILL.md under 500 lines - Move details to references/
- Use clear naming - Lowercase with hyphens (e.g.,
ct-brain-analysis) - Include triggers - Add phrases that should activate the skill
- No secrets - Never commit API keys, credentials, or PHI
Integration Docs
- Complete coverage - Include auth, endpoints, examples
- Verify accuracy - Test endpoints work as documented
- Use standard formats - Follow existing integration doc patterns
- Use the template - Start from
tools/integrations/INTEGRATION_TEMPLATE.md
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.
- 7d ago First seen · 225 lines · 1,675 tokens per session scan A fa4259991e32
clinical-skills CLAUDE.md is an instructions file published in the GitHub repository aizech/clinical-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,675 tokens to every session, about $0.0084 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.