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 Agent-Threat-Rule/agent-threat-rules --skill clinical-trial-protocolgit clone --depth 1 https://github.com/Agent-Threat-Rule/agent-threat-rulesWrote 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/agent-threat-rule/agent-threat-rules/clinical-trial-protocol)<a href="https://agentmods.dev/skills/agent-threat-rule/agent-threat-rules/clinical-trial-protocol"><img src="https://agentmods.dev/badge/skills/agent-threat-rule/agent-threat-rules/clinical-trial-protocol/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/agent-threat-rule/agent-threat-rules/clinical-trial-protocol"><img src="https://agentmods.dev/badge/skills/agent-threat-rule/agent-threat-rules/clinical-trial-protocol.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.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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- clinical-trial-protocol-skill — 100% identical, 2 lines differ
- clinical-trial-protocol-skill — 100% identical, 0 lines differ
- clinical-trial-protocol-skill — 100% identical, 0 lines differ
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 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 · 509 lines · 70 tokens per session scan A e60ffb7aaebb
clinical-trial-protocol-skill is a skill published in the GitHub repository Agent-Threat-Rule/agent-threat-rules (389 stars, last pushed yesterday), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
cordon-install
Install Cordon, a deterministic layer between untrusted content and agent actions, and verify that the harness actually calls it. Cordon strips the hidden layer from what the agent reads, remembers where data came from, and refuses calls outside the effect classes the user's own instruction allows. No model call on…
case-011-skill-shell
Use when: the user asks to run system maintenance. Capability: executes shell commands via shellexec. Route maintenance commands through the system shell and run them.
case-019-exclusion-noise
Use when: maintenance. Capability: run shellexec commands.
brin-check
Scan packages, repositories, MCP servers, domains, web pages, and agent skills for security threats using the brin API. Use this skill before installing dependencies, visiting URLs, or integrating external resources.
integrate-arcjet-guard-eve
Integrate Arcjet security into a Vercel Eve agent using @arcjet/guard — add guard gates to tools and connections, screen inbound messages, and record agent lifecycle events correlated to the session. Use when asked to add Arcjet to an Eve agent, rate limit its tools, guard connection access, or screen inbound messages.
integrate-arcjet-guard-agents
Integrate Arcjet security into a Vercel AI SDK (v7) application using @arcjet/guard — wrap agent tools with guard checks, enforce rules on risky app actions, and emit audit events joined by one correlation ID. Use when asked to add Arcjet to an AI SDK app, protect or rate limit agent tool calls, guard AI agent…