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 LuuOW/meridian-mcp --skill uncertainty-quantificationgit clone --depth 1 https://github.com/LuuOW/meridian-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/luuow/meridian-mcp/uncertainty-quantification)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/uncertainty-quantification"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/uncertainty-quantification/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/luuow/meridian-mcp/uncertainty-quantification"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/uncertainty-quantification.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.00097 | $0.01723 |
| Opus 5 | $0.00048 | $0.00861 |
| Sonnet 5 | $0.00019 | $0.00345 |
| Haiku 4.5 | $0.00010 | $0.00172 |
Grade A, and why
uncertainty-quantification 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uncertainty-quantification
When to invoke
- Parsing statistical claims from research papers (σ, p-value, Bayes factor, credible interval, confidence interval)
- Writing your own outputs — deciding between "certain", "likely", "possible"
- Composing probabilities from multiple independent signals
- Auditing an LLM classifier that outputs binary yes/no when a probability would be more useful
- Reconciling frequentist and Bayesian claims ("this is 3σ" vs "the posterior concentrates at…")
The 5 families of uncertainty you'll encounter
- Statistical (aleatoric) — measurement noise, sampling variance. Quantified by error bars, σ, confidence intervals.
- Systematic — instrumental bias, modeling approximations, calibration drift. Usually larger than stat and harder to quote.
- Epistemic — lack of knowledge that could be reduced with more data or better models. What Bayesian priors encode.
- Model uncertainty — is the underlying model even right? (Often the largest uncertainty, almost never quoted)
- Linguistic / representational — "we observed" vs "we infer" vs "we estimate". Words that look precise but hide choices.
Decoding "3σ" (frequentist)
- σ = standard deviation. "3σ detection" = ~99.73% of Gaussian bulk; p ≈ 2.7×10⁻³ one-tailed, 2.7×10⁻⁴ two-tailed.
- Local vs global significance matters enormously:
- Local: p-value at one specific look
- Global: corrected for the "look-elsewhere effect" across many trials
- A paper claiming "3σ local, 1.5σ global" = essentially not a detection.
- HEP convention:
- 2–3σ: "evidence for"
- 3–5σ: "strong evidence" (but still one trial-factor away from noise)
- ≥5σ: "observation" / "discovery"
- Cosmology/astro convention is more relaxed; 3σ often counted as a result.
Red flag: a claim of "3σ" without stating local-vs-global is almost always local only.
Bayesian alternatives
- Credible interval (CI): "with probability 95%, θ ∈ [a, b] given the data and prior"
- Bayes factor (BF): ratio of likelihoods under competing hypotheses
- BF < 3: barely worth mentioning
- 3 ≤ BF < 20: moderate evidence
- 20 ≤ BF < 150: strong evidence
- BF ≥ 150: decisive
- Posterior probability: P(hypothesis | data) directly — the quantity most people think σ represents but doesn't.
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.
- 9d ago First seen · 133 lines · 97 tokens per session scan A 4eb269d70c3f
uncertainty-quantification is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 1,723 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-09-03.
Other skills, from other repositories
drug-discovery
Drug discovery: ChEMBL search, drug-likeness, interactions.
coding-hcc-risk-adjustment
Maps chronic conditions extracted by OpenMed to CMS-HCC V28 risk-adjustment categories and estimates a RAF (Risk Adjustment Factor) score as decision support. Use when the user wants to surface risk-adjustable diagnoses from notes, map ICD-10-CM codes to HCC categories, estimate or reconcile a patient/panel RAF, find…
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…
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…
structuring-radiology-reports
Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression)…
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…