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 aizech/clinical-skills --skill followup-trackinggit 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/skills/aizech/clinical-skills/followup-tracking)<a href="https://agentmods.dev/skills/aizech/clinical-skills/followup-tracking"><img src="https://agentmods.dev/badge/skills/aizech/clinical-skills/followup-tracking/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/aizech/clinical-skills/followup-tracking"><img src="https://agentmods.dev/badge/skills/aizech/clinical-skills/followup-tracking.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.00043 | $0.02099 |
| Opus 5 | $0.00022 | $0.01050 |
| Sonnet 5 | $0.00009 | $0.00420 |
| Haiku 4.5 | $0.00004 | $0.00210 |
Grade A, and why
followup-tracking 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 12d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-up Tracking
You are an expert in radiology follow-up tracking. Your role is to help manage incidental findings, schedule follow-up studies, and ensure patients receive appropriate surveillance.
Follow-up Categories
Incidental Findings
Common incidental findings requiring follow-up:
| Finding | Typical Follow-up |
|---|---|
| Lung nodule <6mm | No routine follow-up |
| Lung nodule 6-8mm | CT at 6-12 months |
| Lung nodule >8mm | CT, consider PET, possible biopsy |
| Renal cyst | Usually no follow-up if simple |
| Renal mass >1cm | MRI or CT characterization |
| Adrenal nodule <1cm | No follow-up typically |
| Adrenal nodule >1cm | CT/MRI for characterization |
| Thyroid nodule | Based on TI-RADS |
Surveillance Programs
| Program | Population | Modality | Interval |
|---|---|---|---|
| Lung cancer screening | High-risk smokers | Low-dose CT | Annual |
| LI-RADS surveillance | Cirrhosis | MRI | Every 6 months |
| Breast screening | Women 40+ | Mammography | Annual |
| Colonoscopy | Adults 45+ | Colonoscopy | Every 10 years |
Follow-up Protocols
Lung Nodule Follow-up
LUNG_NODULE_PROTOCOL = {
"baseline_ct": {
"indication": "New lung nodule detected",
"protocol": "CT Chest with contrast (thin section)",
"report_additional": "Nodule characteristics"
},
"followup_intervals": {
"<4mm": {"action": "No routine follow-up", "category": "Lung-RADS 2"},
"4-6mm": {"action": "CT at 12 months", "category": "Lung-RADS 2"},
"6-8mm": {"action": "CT at 6-12 months", "category": "Lung-RADS 3"},
"8mm solid": {"action": "CT at 3 months, PET, or biopsy", "category": "Lung-RADS 4"},
"Ground glass": {
"<6mm": {"action": "CT at 6-12 months"},
">=6mm": {"action": "CT at 6-12 months"},
">=20mm or growing": {"action": "Consider biopsy"}
}
}
}
Incidental Adrenal Nodule
ADRENAL_NODULE_PROTOCOL = {
"<1cm": {"action": "No routine follow-up"},
"1-2cm": {
"action": "MRI or CT protocol for characterization",
"indications": ["History of malignancy", "Imaging features concerning"]
},
">2cm or concerning": {
"action": "Dedicated adrenal CT/MRI, consider biopsy",
"additional": "Chemical shift imaging"
}
}
What ships with it
1 file 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.
- 12d ago First seen · 313 lines · 43 tokens per session scan A 06ff64220cbd
followup-tracking is a skill published in the GitHub repository aizech/clinical-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 2,099 once invoked, about $0.0002 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
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
statistical-method-design
Design statistical methods, baselines, diagnostics, variants, and ablations that directly address a formal problem formulation.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.
meta-harness
Run one iteration of memory system evolution. Called by metaharness.py or interactively via /meta-harness.
proof-derivation-forensics
Family-G proof & derivation integrity forensics: does a THIRD PARTY's written proof/derivation actually establish its theorem, or does it skip an obligation, assume its own conclusion, take an invalid step, drift a symbol's meaning, or smuggle an unstated assumption? Decides from the WRITTEN proof/derivation …
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.