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 agentmods add skills/synthetic-sciences/openscience/clinical-decision-supportnpx skills add synthetic-sciences/openscience --skill clinical-decision-supportgit clone --depth 1 https://github.com/synthetic-sciences/openscienceWhat 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 | $0.00097 | $0.05883 |
| Opus 5 | $0.00048 | $0.02942 |
| Sonnet 5 | $0.00019 | $0.01177 |
| Haiku 4.5 | $0.00010 | $0.00588 |
Grade A, and why
clinical-decision-support 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 yesterday.
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
8 near-identical copies found in the catalogue:
- clinical-decision-support — 98% identical, 8 lines differ
- clinical-decision-support — 95% identical, 3 lines differ
- clinical-decision-support — 95% identical, 11 lines differ
- clinical-decision-support — 95% identical, 10 lines differ
- clinical-decision-support — 94% identical, 10 lines differ
- clinical-decision-support — 94% identical, 10 lines differ
- clinical-decision-support — 94% identical, 8 lines differ
- clinical-decision-support-hardened — 94% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 508 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Decision Support Documents
Description
Generate professional clinical decision support (CDS) documents for pharmaceutical companies, clinical researchers, and medical decision-makers. This skill specializes in analytical, evidence-based documents that inform treatment strategies and drug development:
- Patient Cohort Analysis - Biomarker-stratified group analyses with statistical outcome comparisons
- Treatment Recommendation Reports - Evidence-based clinical guidelines with GRADE grading and decision algorithms
All documents are generated as publication-ready LaTeX/PDF files optimized for pharmaceutical research, regulatory submissions, and clinical guideline development.
Note: For individual patient treatment plans at the bedside, use the treatment-plans skill instead. This skill focuses on group-level analyses and evidence synthesis for pharmaceutical/research settings.
Writing Style: For publication-ready documents targeting medical journals, consult the venue-templates skill's medical_journal_styles.md for guidance on structured abstracts, evidence language, and CONSORT/STROBE compliance.
Capabilities
Document Types
Patient Cohort Analysis
- Biomarker-based patient stratification (molecular subtypes, gene expression, IHC)
- Molecular subtype classification (e.g., GBM mesenchymal-immune-active vs proneural, breast cancer subtypes)
- Outcome metrics with statistical analysis (OS, PFS, ORR, DOR, DCR)
- Statistical comparisons between subgroups (hazard ratios, p-values, 95% CI)
- Survival analysis with Kaplan-Meier curves and log-rank tests
- Efficacy tables and waterfall plots
- Comparative effectiveness analyses
- Pharmaceutical cohort reporting (trial subgroups, real-world evidence)
Treatment Recommendation Reports
- Evidence-based treatment guidelines for specific disease states
- Strength of recommendation grading (GRADE system: 1A, 1B, 2A, 2B, 2C)
- Quality of evidence assessment (high, moderate, low, very low)
- Treatment algorithm flowcharts with TikZ diagrams
- Line-of-therapy sequencing based on biomarkers
- Decision pathways with clinical and molecular criteria
- Pharmaceutical strategy documents
- Clinical guideline development for medical societies
What ships with it
19 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/biomarker_report_template.tex 13 KB
- assets/clinical_pathway_template.tex 8.1 KB
- assets/cohort_analysis_template.tex 12 KB
- assets/color_schemes.tex 6.9 KB
- assets/example_gbm_cohort.md 9.1 KB
- assets/recommendation_strength_guide.md 11 KB
- assets/treatment_recommendation_template.tex 18 KB
- README.md 4.9 KB
- references/biomarker_classification.md 29 KB
- references/clinical_decision_algorithms.md 21 KB
- references/evidence_synthesis.md 33 KB
- references/outcome_analysis.md 24 KB
- references/patient_cohort_analysis.md 16 KB
- references/treatment_recommendations.md 19 KB
- scripts/biomarker_classifier.py 13 KB runs code
- scripts/build_decision_tree.py 15 KB runs code
- scripts/create_cohort_tables.py 17 KB runs code
- scripts/generate_survival_analysis.py 15 KB runs code
- scripts/validate_cds_document.py 12 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.
- yesterday First seen · 508 lines · 97 tokens per session scan A 0bc44b745344
clinical-decision-support is a skill published in the GitHub repository synthetic-sciences/openscience (3,362 stars, last pushed 2d ago), licensed Apache-2.0. It adds 97 tokens to every session and 5,883 once invoked, about $0.0005 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 skills, from other repositories
github-pr-review-session
Human-reviewer co-pilot for ZeroClaw PR reviews. Use this skill when the user wants to review a specific PR as themselves, re-review a PR after author changes, work through a queue of PRs, check what's still open on a PR, or post a formal review verdict. Trigger on: 'review 1234', 'can you look at PR #1234'…
squash-merge
Squash-merge a PR into zeroclaw-labs/zeroclaw master with fully preserved commit history in the squash message body. Use this skill when the user explicitly mentions squash-merging, merging a specific PR number, landing a PR, or 合入 — e.g. "squash-merge #123", "merge PR 456", "land #789", "合入 #123", "/squash-merge…
github-pr
Open or update a GitHub Pull Request for ZeroClaw. Handles creating new PRs with a fully filled-out template body, and updating existing PRs (title, body sections, labels, comments). Use this skill whenever the user wants to open a PR, create a pull request, update a PR, edit PR description, add labels to a PR, or…
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
feature-matrix-parity
Update the OpenClaw and Hermes comparison columns of the ZeroClaw feature-and-support matrix. Use this skill when the user wants to refresh, fill, or verify parity data in docs/book/feature-matrix-parity.toml, add a new comparison row or section to the feature matrix, or re-walk the competitor repos for support…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…