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 u9401066/rootcause-mcp --skill pubmed-search-mcp-harnessgit 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-search-mcp-harness)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/pubmed-search-mcp-harness"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/pubmed-search-mcp-harness/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-search-mcp-harness"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/pubmed-search-mcp-harness.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.00041 | $0.00408 |
| Opus 5 | $0.00020 | $0.00204 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
pubmed-search-mcp-harness 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 11d 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
91% identical to pubmed-search-mcp-harness — 2 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.
What it actually says
PubMed Search MCP: Cline Harness Skill
Use this skill when working in the PubMed Search MCP repository with Cline and you need a dependable loop for literature-search tools, pipeline behavior, and release checks.
What To Use First
- Rules:
.clinerules/ - Workflows:
.clinerules/workflows/- Run
/pubmed-full-check.mdfor local gates. - Run
/pubmed-skills-audit.mdafter changing skills or rules. - Run
/pubmed-release-publish.mdfor release prep.
- Run
- User-facing research skills:
.claude/skills/pubmed-*and.claude/skills/pipeline-persistence.- If a
.claude/skillsinstruction conflicts with current implementation, prefer.clinerules/.
- If a
Canonical Commands
- Lint:
uv run ruff check . - Format check:
uv run ruff format --check . - Types:
uv run mypy src/ tests/ - Tests:
uv run pytest - Tool docs sync:
uv run python scripts/count_mcp_tools.py --update-docs - Skill audit:
python3 scripts/check_cline_skills.py
Research Guardrails
- Prefer
unified_searchas the primary multi-source entrypoint. - Preserve session/pipeline state instead of relying on agent memory.
- Use
build_research_chronicleandread_research_chroniclefor durable research-history artifacts; the former timeline tools are no longer public. - Respect NCBI email/API-key policy and institutional access configuration.
- Keep exported citations reproducible: PMIDs, DOI, source, date filters, and query strategy matter.
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.
- 11d ago First seen · 38 lines · 41 tokens per session scan A 5d71d90750a1
pubmed-search-mcp-harness is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 8d ago), licensed Apache-2.0. It adds 41 tokens to every session and 408 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to pubmed-search-mcp-harness, differing in 2 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…
exporting-to-fhir
Convert OpenMed NER output (entities from openmed.analyzetext) into FHIR R4 resources — Condition, MedicationStatement, Observation — using OpenMed's built-in FHIR R4 export helpers in openmed.clinical.exporters. Covers the verified CodeableConcept builder (coding, codeableconcept, systemuri), deterministic fullUrl…
annotating-variants
Annotates VCF variants and normalizes HGVS nomenclature with public, license-free annotators (Ensembl VEP REST, VEP/SnpEff/ANNOVAR offline) and links variants to gnomAD population frequencies and the clinical context OpenMed extracts. Use when the user wants to predict variant consequences, map HGVS to genomic…
assembling-fhir-bundles
Package multiple FHIR R4 resources produced from OpenMed output into a single valid transaction Bundle ready to POST to an EHR, using OpenMed's verified bundle assembler openmed.clinical.exporters.fhir.tobundle. Covers deterministic urn:uuid fullUrls, automatic in-Bundle reference rewriting, request blocks…
auditing-part11-trails
Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…
batch-processing-clinical-text
Run large-scale batch NER, PII extraction, or de-identification over many clinical notes on-device with OpenMed, with sharding, checkpointing, resumability, and append-only JSONL output. Use when the user needs to process a corpus or folder of notes, de-identify a dataset, run NER over thousands of documents, build a…