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 agentmods add commands/choxos/biostatagent/run-diagnosticsgit 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/commands/choxos/biostatagent/run-diagnostics)<a href="https://agentmods.dev/commands/choxos/biostatagent/run-diagnostics"><img src="https://agentmods.dev/badge/commands/choxos/biostatagent/run-diagnostics.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 | $0.00014 | $0.01578 |
| Opus 5 | $0.00007 | $0.00789 |
| Sonnet 5 | $0.00003 | $0.00316 |
| Haiku 4.5 | $0.00001 | $0.00158 |
Grade A, and why
run-diagnostics 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 3d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model Execution and Diagnostics Workflow
You are helping the user run and diagnose their Bayesian model.
Step 1: Identify Model and Data
Determine:
- Model language: Stan / JAGS / WinBUGS / PyMC
- Data source:
- User-provided data
- Generate synthetic test data
Step 2: Generate Test Data (if needed)
Use @test-runner to create appropriate synthetic data:
For Regression Models
set.seed(42)
N <- 100
K <- 3
X <- matrix(rnorm(N * K), N, K)
true_beta <- c(0.5, -0.3, 0.8)
true_sigma <- 1
y <- X %*% true_beta + rnorm(N, 0, true_sigma)
stan_data <- list(N = N, K = K, X = X, y = as.vector(y))
For Hierarchical Models
set.seed(42)
J <- 8
N_per_group <- 20
true_mu <- 5
true_tau <- 3
true_theta <- rnorm(J, true_mu, true_tau)
y <- unlist(lapply(1:J, function(j) rnorm(N_per_group, true_theta[j], 2)))
group <- rep(1:J, each = N_per_group)
stan_data <- list(N = J * N_per_group, J = J, group = group, y = y)
Step 3: Execute Model
Stan (cmdstanr)
library(cmdstanr)
# Compile
mod <- cmdstan_model("model.stan")
# Short test run
fit <- mod$sample(
data = stan_data,
seed = 12345,
chains = 2,
parallel_chains = 2,
iter_warmup = 500,
iter_sampling = 500,
refresh = 100
)
JAGS (R2jags)
library(R2jags)
fit <- jags(
data = jags_data,
parameters.to.save = c("mu", "sigma", "theta"),
model.file = "model.txt",
n.chains = 2,
n.iter = 2000,
n.burnin = 1000,
progress.bar = "text"
)
PyMC (Python)
import pymc as pm
import arviz as az
import numpy as np
# Define model
with pm.Model() as model:
# Priors
mu = pm.Normal("mu", mu=0, sigma=10)
sigma = pm.HalfNormal("sigma", sigma=1)
# Likelihood
y_obs = pm.Normal("y_obs", mu=mu, sigma=sigma, observed=y_data)
# Sample
trace = pm.sample(
draws=1000,
tune=1000,
chains=2,
cores=2,
random_seed=12345,
return_inferencedata=True
)
# Diagnostics
print(az.summary(trace))
az.plot_trace(trace)
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.
- 3d ago First seen · 247 lines · 14 tokens per session scan A 128095f11e06
run-diagnostics is a command published in the GitHub repository choxos/BiostatAgent (11 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,578 once invoked, about $0.0001 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 commands, from other repositories
check-dev
Type-check a Z specification with fuzz.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
render-figures
Compile all .tex and .typ figure files in a directory.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.