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 fergupa/claude_plugins --skill clinical-trial-protocolgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/clinical-trial-protocol)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/clinical-trial-protocol"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/clinical-trial-protocol.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.00070 | $0.04686 |
| Opus 5 | $0.00035 | $0.02343 |
| Sonnet 5 | $0.00014 | $0.00937 |
| Haiku 4.5 | $0.00007 | $0.00469 |
Grade A, and why
clinical-trial-protocol-skill 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 6d 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-trial-protocol-skill — 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 — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Trial Protocol Skill
⚠️ EXECUTION CONTROL - READ THIS FIRST
CRITICAL: This orchestrator follows a SIMPLE START approach:
- Display the welcome message FIRST (shown in "Startup: Welcome and Confirmation" section below)
- Ask user to confirm they're ready to proceed - Wait for confirmation (yes/no)
- Jump directly into Full Workflow Logic - Automatically run subskills sequentially
- Do NOT pre-read subskill files - Subskills are loaded on-demand only when their step executes
Why this matters:
- Pre-reading all subskills wastes context and memory
- Subskills should only load when actually needed during execution
- Workflow automatically handles resuming from existing waypoints
Overview
This skill generates clinical trial protocols for medical devices or drugs using a modular, waypoint-based architecture
What This Skill Does
Starting with an intervention idea (device or drug), this orchestrated workflow offers two modes:
🔬 Research Only Mode (Steps 0-1): 0. Initialize Intervention - Collect device or drug information
- Research Similar Protocols - Find similar trials, FDA guidance, and published protocols
- Deliverable: Comprehensive research summary as formatted .md artifact
📄 Full Protocol Mode (Steps 0-5): 0. Initialize Intervention - Collect device or drug information
- Research Similar Protocols - Find similar trials, FDA guidance, and published protocols
- Protocol Foundation - Generate protocol sections 1-6 (foundation, design, population)
- Protocol Intervention - Generate protocol sections 7-8 (intervention details)
- Protocol Operations - Generate protocol sections 9-12 (assessments, statistics, operations)
- Generate Protocol - Create professional file ready for stakeholder review
Architecture
Waypoint-Based Design
All analysis data is stored in waypoints/ directory as JSON/markdown files:
waypoints/
├── intervention_metadata.json # Intervention info, status, initial context
├── 01_clinical_research_summary.json # Similar trials, FDA guidance, recommendations
├── 02_protocol_foundation.md # Protocol sections 1-6 (Step 2)
├── 03_protocol_intervention.md # Protocol sections 7-8 (Step 3)
├── 04_protocol_operations.md # Protocol sections 9-12 (Step 4)
├── 02_protocol_draft.md # Complete protocol (concatenated in Step 4)
├── 02_protocol_metadata.json # Protocol metadata
└── 02_sample_size_calculation.json # Statistical sample size calculation
What ships with it
9 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/FDA-Clinical-Protocol-Template.md 173 KB
- LICENSE.txt 10 KB
- references/00-initialize-intervention.md 8.6 KB
- references/01-research-protocols.md 19 KB
- references/02-protocol-foundation.md 40 KB
- references/03-protocol-intervention.md 33 KB
- references/04-protocol-operations.md 81 KB
- references/05-concatenate-protocol.md 8.8 KB
- scripts/sample_size_calculator.py 15 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.
- 6d ago First seen · 509 lines · 70 tokens per session scan A e60ffb7aaebb
clinical-trial-protocol-skill is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 4,686 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to clinical-trial-protocol-skill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…