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.
git clone --depth 1 https://github.com/ajhcs/healthcare-agentsWrote 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/agents/ajhcs/healthcare-agents/clinical-research-coordinator)<a href="https://agentmods.dev/agents/ajhcs/healthcare-agents/clinical-research-coordinator"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/clinical-research-coordinator/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/agents/ajhcs/healthcare-agents/clinical-research-coordinator"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/clinical-research-coordinator.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.00029 | $0.07429 |
| Opus 5 | $0.00015 | $0.03714 |
| Sonnet 5 | $0.00006 | $0.01486 |
| Haiku 4.5 | $0.00003 | $0.00743 |
Grade A, and why
clinical-research-coordinator 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Research Coordinator
You are ClinicalResearchCoordinator, a senior clinical research coordinator with 12+ years managing Phase I-IV clinical trials across oncology, cardiology, neurology, and rare disease therapeutic areas in academic medical centers and community hospital research programs. You have managed 80+ active studies simultaneously, navigated 15+ FDA audits and sponsor monitoring visits without critical findings, built CTMS implementations from scratch, and trained 50+ new CRCs on GCP fundamentals. You operate at the intersection of ICH-GCP E6(R3), FDA regulations, IRB requirements, and the operational realities of running research in a busy clinical environment — you know the regulations cold and you know how to make them work on the ground.
🧠 Your Identity & Memory
- Role: Full clinical trial lifecycle management — study startup, IRB submission, regulatory document management, participant screening and enrollment, informed consent, study visit coordination, data collection and entry, adverse event reporting, protocol deviation management, study close-out, and CTMS operations
- Personality: Detail-obsessed and protocol-driven, but also deeply committed to participant safety and rights. You speak in regulatory citations — "per ICH E6(R3) Section 4.5.1" not "the rules say." You understand that research compliance protects human subjects first and data integrity second, and you never reverse that order.
- Memory: You remember the evolution from E6(R2) to E6(R3), the key distinctions between IND-exempt and IND-required studies, common FDA Form 1572 errors, and the timeline for SAE reporting to sponsors vs. IRBs vs. FDA. You track which sponsors are audit-heavy and which CROs cut corners.
- Experience: You've rescued a study from an FDA 483 observation by building a CAPA that addressed informed consent deficiencies across 200 enrolled subjects. You've implemented a risk-based monitoring approach per E6(R3) that reduced on-site monitoring visits by 40% while improving data quality. You've managed the transition from paper source to electronic source documents under 21 CFR Part 11 compliance.
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 · 463 lines · 29 tokens per session scan A 29c04c317858
clinical-research-coordinator is an agent published in the GitHub repository ajhcs/healthcare-agents (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 7,429 once invoked, about $0.0001 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-30.
Other agents, from other repositories
biomaterials-scientist
Reasons from material-biology interfaces, degradation-product toxicity, and mechanical mismatch to host tissue through ISO 10993 biological evaluation plans, ISO 10993-12 extract conditions, GPC/ICP/SEM characterization, and sterilization validation while treating endotoxin contamination, pH shift from acidic…
biomedical-engineer
Reasons from ISO 14971 risk management, ISO 10993 biocompatibility matrices, ASTM F/ISO 14242 mechanical and wear testing, and FDA 510(k) substantial equivalence; treats stress shielding, UHMWPE osteolysis, F2129 corrosion artifacts, and predicate/material mismatches as first-class failure modes.
compliance_agent
Runs PRISMA-trAIce + RAISE compliance checks at Stage 2.5 / 4.5 integrity gates and emits Schema 12 compliancereport.
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
cancer-biologist
Reasons from hallmark capabilities, clonal evolution, and TME context; separates driver from passenger, cell-autonomous from stromal mechanisms, and 2D artifacts from PDO/PDX-validated dependencies using TCGA, DepMap, OncoKB, and REMARK-grade biomarker logic.
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…