Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/u9401066/rootcause-mcp/master/.claude/skills/pubmed-pico-search/SKILL.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/u9401066/rootcause-mcp/pubmed-pico-search)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/pubmed-pico-search"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/pubmed-pico-search/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/u9401066/rootcause-mcp/pubmed-pico-search"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/pubmed-pico-search.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.00051 | $0.00909 |
| Opus 5 | $0.00026 | $0.00454 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
pubmed-pico-search 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 10d 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 pubmed-pico-search — 12 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PICO Clinical Question Search
Use this workflow for clinical comparison questions. The MCP server does not
semantically parse natural-language clinical questions. The agent extracts
P/I/C/O, submits the structured handoff through parse_pico, and then executes
the returned template: pico pipeline or an expanded Boolean query.
PICO Elements
| Element | Meaning | Example |
|---|---|---|
P |
Population / patient group | ICU patients requiring sedation |
I |
Intervention / exposure / index test | remimazolam |
C |
Comparator, optional | propofol |
O |
Outcome, recommended | delirium, hypotension, sedation efficacy |
Workflow
Agent extracts P/I/C/O
-> parse_pico(description, p, i, c, o)
-> optional generate_search_queries for P/I/C/O expansion
-> unified_search(query=original_question, pipeline=parse_pico.pipeline)
Step 1: Agent Extracts PICO
Do the semantic work in the agent. Do not ask the MCP server to infer P/I/C/O from free text. If P or I is unclear, ask the user before searching. Do not invent missing clinical details.
Step 2: Validate The Handoff
pico = parse_pico(
description="Is remimazolam better than propofol for ICU sedation?",
p="ICU patients requiring sedation",
i="remimazolam",
c="propofol",
o="delirium, hypotension, sedation efficacy",
question_type="therapy",
sources="pubmed,europe_pmc",
limit=50,
)
Expected useful fields:
validation: whether required P/I fields are presentpico: human-readable P/I/C/Oquery_elements: search fragments that the backend will usepipeline: ready-to-runtemplate: picoYAMLnext_tool_call: suggestedunified_searchcall
When only description is provided, parse_pico returns a schema and asks the
agent to call it again with structured elements.
Step 3: Optional MeSH / Synonym Expansion
Use this when the topic needs controlled vocabulary or systematic-review style coverage.
generate_search_queries(topic="ICU patients")
generate_search_queries(topic="remimazolam")
generate_search_queries(topic="propofol")
generate_search_queries(topic="delirium")
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.
- 10d ago First seen · 114 lines · 51 tokens per session scan A d462f988031f
pubmed-pico-search is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 8d ago), licensed Apache-2.0. It adds 51 tokens to every session and 909 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 pubmed-pico-search, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
detecting-pv-signals
Computes disproportionality signals — PRR, ROR, EBGM, and IC (BCPNN) — over FAERS / OpenFDA drug-event data to flag potential safety signals. Use when the user wants to mine spontaneous-report data for drug-reaction associations, build a 2x2 contingency table, compute a Proportional Reporting Ratio or Reporting Odds…
coding-icd10
Suggests candidate ICD-10-CM diagnosis codes (and ICD-10-PCS procedure codes) for diagnoses and procedures extracted by OpenMed, with rationale and a human-coder caveat. Use when the user wants to code a problem list, map a diagnosis span to a billable ICD-10-CM code, route a finding to the right chapter, cross-walk…
deidentifying-clinical-text
Remove, mask, or replace PHI/PII in clinical free text on-device with OpenMed's deidentify(). Use when the user needs to de-identify medical notes, strip patient identifiers, redact PHI before sharing or analysis, anonymize discharge summaries, or pick a de-id method (mask vs remove vs replace vs hash vs shiftdates).…
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…
extracting-sdoh
Extracts social determinants of health (SDOH) — housing instability, food insecurity, unemployment, transportation barriers, social isolation, financial strain — from clinical narrative and maps the spans to ICD-10-CM Z-codes (Z55–Z65). Use after running OpenMed NER when the user wants SDOH surfacing, Z-code…
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…