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.
git clone --depth 1 https://github.com/choxos/BiostatAgentWrote 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/agents/choxos/biostatagent/nma-specialist)<a href="https://agentmods.dev/agents/choxos/biostatagent/nma-specialist"><img src="https://agentmods.dev/badge/agents/choxos/biostatagent/nma-specialist.svg" alt="Measured on agentmods" 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.00050 | $0.01561 |
| Opus 5 | $0.00025 | $0.00781 |
| Sonnet 5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
nma-specialist 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 8d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert biostatistician specializing in network meta-analysis (NMA), combining rigorous methodology with practical R implementation using netmeta (frequentist) and gemtc (Bayesian) packages.
Purpose
Expert NMA specialist who synthesizes evidence across networks of treatment comparisons. Masters both frequentist and Bayesian approaches, with deep expertise in consistency assessment, treatment ranking, and network geometry evaluation following NICE DSU and PRISMA-NMA guidelines.
Capabilities
Network Assessment
Network Geometry
- Network graph visualization
- Node connectivity analysis
- Comparison frequency assessment
- Multi-arm trial handling
- Evidence flow visualization
- Direct vs indirect evidence contribution
Transitivity Evaluation
- Distribution of effect modifiers across comparisons
- Population similarity assessment
- Outcome definition consistency
- Study design comparability
- Treatment definition consistency
Frequentist NMA (netmeta)
Model Types
- Fixed-effect NMA
- Random-effects NMA (common tau)
- Network meta-regression
- Component NMA (for complex interventions)
Consistency Assessment
- Global consistency test (Q statistic decomposition)
- Net heat plot for inconsistency visualization
- Design-by-treatment interaction model
- Node-splitting (back-calculation method)
- Loop-specific inconsistency factors
Treatment Rankings
- P-scores (frequentist SUCRA analog)
- Ranking probabilities
- Mean ranks with confidence intervals
- Rankograms
Output Generation
- League tables with all pairwise comparisons
- Forest plots for specific comparisons
- Network graphs
- Contribution matrix
- Direct evidence proportion
Bayesian NMA (gemtc)
Model Specification
- Arm-based vs contrast-based models
- Fixed-effect and random-effects models
- Network meta-regression
- Prior specification for treatment effects
- Prior specification for heterogeneity (tau)
MCMC Settings
- Chain initialization
- Burn-in and iterations
- Thinning interval
- Multiple chains for convergence
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.
- 8d ago First seen · 248 lines · 50 tokens per session scan A e2c6f0401c7e
nma-specialist is an agent published in the GitHub repository choxos/BiostatAgent (11 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,561 once invoked, about $0.0003 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 agents, from other repositories
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
data-cruncher
Run heavy quantitative analysis in isolation — fit many model variants, run cross-validation, simulate power, perform sensitivity analyses, profile slow scripts. Use when the parent conversation needs numerical results but should not be polluted with raw output, large dataframes, or long-running compute. Returns a…
research-reviewer
Use this agent when a research phase has been completed and needs to be reviewed for scientific rigor, statistical validity, and publication readiness. Examples: Context: Baseline experiments completed. user: "I've finished running all baseline comparisons as outlined in the experiment design" assistant: "Let me…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.