tooluniverse-pharmacovigilance

tooluniverse-pharmacovigilance is a skill for Claude Code from mims-harvard/ToolUniverse. It costs 96 tokens per session (4,704 once invoked), scanned A, original, Apache-2.0.

A drug-safety analysis workflow that examines reports of unwanted effects, regulatory warnings, clinical-trial findings, and genetic factors. FAERS is the FDA database of adverse-event reports submitted after medicines are used.

In plain words
What is it for?
Use it to investigate adverse events, drug safety concerns, black-box warnings, risk factors, safety signals, and changes to official drug labels.
Why use it?
It helps identify possible safety signals, weigh their strength and seriousness, and compare evidence from several sources instead of relying on isolated reports.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the tooluniverse plugin — 162 skills, 8 commands, 1 agent, 1 hook, 1 MCP server shipped together

Good fit Use it to investigate adverse events, drug safety concerns, black-box warnings, risk factors, safety signals, and changes to official drug labels.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance
About the project

ToolUniverse is a collection of tools, interfaces, and supporting components for building AI systems that perform scientific work. It is for developers creating AI scientist agents that use APIs, databases, machine-learning tools, and domain-specific utilities. The catalogue includes skills, commands, an MCP server, an agent, and a hook for working with the ecosystem.

mims-harvard/ToolUniverse · 1,744 stars · on GitHub · aiscientist.tools

Install

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.

Any agent
npx skills add mims-harvard/ToolUniverse --skill tooluniverse-pharmacovigilance
Clone the repo
git clone --depth 1 https://github.com/mims-harvard/ToolUniverse

Made for: Claude Code.

Or install tooluniverse, the plugin that ships this one along with the rest of its 162 skills, 8 commands, 1 agent, 1 hook, 1 MCP server.

Wrote 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.

agentmods badge for tooluniverse-pharmacovigilance

README.md
[![agentmods](https://agentmods.dev/badge/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance/github.svg)](https://agentmods.dev/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance)
Your own site
<a href="https://agentmods.dev/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance"><img src="https://agentmods.dev/badge/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance/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.

agentmods 80×15 button for tooluniverse-pharmacovigilance

Your own site · 80×15
<a href="https://agentmods.dev/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance"><img src="https://agentmods.dev/badge/skills/mims-harvard/tooluniverse/tooluniverse-pharmacovigilance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 29 Mar 2026
  • Snyk warn 29 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.04704
Opus 5.5 $0.00038 $0.01882
Sonnet 5.5 $0.00019 $0.00941
Haiku 4.5 $0.00010 $0.00470

Measured 10d ago against content hash 1cc1349b5ced, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tooluniverse-pharmacovigilance 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.

plugin/skills/tooluniverse-pharmacovigilance/SKILL.md · 351 lines

How it starts

The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.

COMPUTE, DON'T DESCRIBE

When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.

Pharmacovigilance Safety Analyzer

Systematic drug safety analysis using FAERS adverse event data, FDA labeling, PharmGKB pharmacogenomics, and clinical trial safety signals.

KEY PRINCIPLES:

  1. Report-first approach - Create report file FIRST, update progressively
  2. Signal quantification - Use disproportionality measures (PRR, ROR)
  3. Severity stratification - Prioritize serious/fatal events
  4. Multi-source triangulation - FAERS, labels, trials, literature
  5. Pharmacogenomic context - Include genetic risk factors
  6. Actionable output - Risk-benefit summary with recommendations
  7. English-first queries - Always use English drug names in tool calls

When to Use

Apply when user asks:

  • "What are the safety concerns for [drug]?"
  • "What adverse events are associated with [drug]?"
  • "Is [drug] safe? What are the risks?"
  • "Compare safety profiles of [drug A] vs [drug B]"
  • "Pharmacovigilance analysis for [drug]"

Clinical Reasoning Framework

Reasoning Strategy 1: On-Target vs Off-Target Thinking

Ask: is this adverse effect a predictable extension of the drug's mechanism (on-target), or something the mechanism doesn't explain (off-target)? On-target effects are dose-dependent and predictable. Off-target effects are often idiosyncratic and harder to predict.

How to apply this:

  1. Look up the drug's primary mechanism of action (use ChEMBL or DailyMed label)
  2. For each reported adverse event, ask: "Does this follow logically from what the drug does to its target?" If yes, it is on-target toxicity — expect dose-dependence and manage with dose reduction
  3. If the adverse event cannot be explained by the primary mechanism, consider off-target receptor binding or reactive metabolite formation. These require different management (drug discontinuation, not dose adjustment)
  4. Use KEGG pathway data to identify metabolic routes that could produce toxic intermediates

Read the full file on GitHub · 351 lines

Files

What ships with it

6 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.

Changes

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.

  1. 10d ago Changed · +17 lines · +20 tokens per session 1cc1349b5ced
  2. 1mo ago First seen · 334 lines · 76 tokens per session scan A bfb61e56402e

Subscribe to this mod's changes

tooluniverse-pharmacovigilance is a skill published in the GitHub repository mims-harvard/ToolUniverse (1,744 stars, last pushed yesterday), licensed Apache-2.0. It adds 96 tokens to every session and 4,704 once invoked, about $0.0004 per session on Opus 5.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-03.

Related

Other skills, from other repositories

ai-agent-tool-routing

Use when designing or reviewing an AI agent tool registry or MCP router: document parameter schemas, caller authorization, execution limits, replay-safe retries and verification evidence.

sickn33/agentic-awesome-skills · 36 tokens

nanoresearch-writing

Draft a LaTeX research paper from all previous stage outputs.

OpenRaiser/NanoResearch · 17 tokens

construct-toy-examples

Generate and analyze simpler examples that satisfy both the assumptions and the conclusion of a theorem statement or subgoal. Use when you are stuck in reasoning and need simpler examples to regain traction, or when you want to see where the assumptions take effect and gain intuition.

frenzymath/Danus · 57 tokens

obtain-immediate-conclusions

Derive immediate mathematical consequences from a theorem statement or subgoal. Use when starting a new problem, branch, or subgoal, or when cheap progress or a cleaner reformulation is needed before deeper proof search.

frenzymath/Danus · 49 tokens

clinical-research-analysis-framework

Guided workflow for statistical and ML analysis of clinical data. Use when planning or executing research analyses on MIMIC, eICU, or similar EHR data. Ensures methodological rigor through structured consultation, assumption checking, and stepwise execution with audit trails.

hannesill/m4 · 59 tokens

apache-iv-score

Calculate APACHE IV (Acute Physiology and Chronic Health Evaluation IV) score for ICU mortality prediction. Use for severity assessment, hospital mortality prediction, ICU benchmarking, or case-mix adjustment. eICU has pre-computed scores; MIMIC-IV requires custom implementation with diagnosis mapping challenges.

hannesill/m4 · 65 tokens