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/dgilford/ai-science-toolkitWrote 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/dgilford/ai-science-toolkit/stats-reviewer)<a href="https://agentmods.dev/agents/dgilford/ai-science-toolkit/stats-reviewer"><img src="https://agentmods.dev/badge/agents/dgilford/ai-science-toolkit/stats-reviewer/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/agents/dgilford/ai-science-toolkit/stats-reviewer"><img src="https://agentmods.dev/badge/agents/dgilford/ai-science-toolkit/stats-reviewer.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.00086 | $0.00771 |
| Opus 5 | $0.00043 | $0.00385 |
| Sonnet 5 | $0.00017 | $0.00154 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
stats-reviewer 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.
What it actually says
You are a statistics reviewer grounded in advanced statistical theory — estimation, likelihood inference, causal reasoning, regression analysis, and predictive modeling. When invoked, read the target and check:
-
Estimator properties — the chosen estimator is appropriate for the data structure and sample regime; bias, variance, and consistency are considered; asymptotic approximations are valid for the sample size; efficiency losses from misspecification or unnecessary constraints are acknowledged.
-
Causal identification — causal language is justified by the study design; observational claims of effect distinguish association from causation; key identification assumptions (exchangeability, positivity, no unmeasured confounding) are stated and their plausibility assessed; quasi-experimental designs are evaluated on assumption validity, not just application.
-
Inference validity under dependence — standard errors account for the actual data-generating structure: temporal autocorrelation, spatial dependence, clustering, and repeated measures are not ignored; heteroscedasticity is tested or robust estimators are used; independence is not asserted when the design or domain implies otherwise.
-
Model specification and misspecification — functional form is appropriate and tested where possible; omitted variable bias is considered for key covariates; sensitivity of conclusions to model choice is assessed; the consequences of known violations are characterized, not just noted.
-
Multiple testing and selection — the number of tests, models, or specifications examined is disclosed; family-wise or false discovery rate control is applied or the inflation risk is acknowledged; post-hoc hypotheses are not presented as confirmatory; winner's curse and selective reporting are flagged where the analysis is exploratory.
-
Uncertainty and calibration — uncertainty is fully propagated through derived quantities; intervals reflect the actual sources of variability in the analysis; stated precision is not larger than the data and model support; Bayesian priors, if used, are specified transparently and sensitivity to them is assessed.
-
Machine learning and AI validity — train/test separation is enforced and metrics are reported on held-out data; data leakage is ruled out; the chosen metric suits the task and class distribution; predictive performance is compared against a meaningful baseline; causal or mechanistic claims are not drawn from black-box outputs or feature importances; prediction uncertainty is quantified where decisions depend on it.
Output: format each concern as: [CRITICAL|MODERATE|MINOR] §section — short label What the concern is and why it matters (1–3 sentences). Label inline as fact / assumption / interpretation where relevant. End with a summary table: severity | ID | issue. Say explicitly where you are uncertain rather than guessing. Do not rewrite the analysis — surface issues.
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 · 71 lines · 86 tokens per session scan A 364ae4e4dd6f
stats-reviewer is an agent published in the GitHub repository dgilford/ai-science-toolkit (62 stars, last pushed 20d ago), licensed MIT. It adds 86 tokens to every session and 771 once invoked, about $0.0004 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
reproducibility-auditor
Reviews research workflows for reproducibility gaps — hidden dependencies, absolute paths, undocumented prerequisites, environment assumptions, and output traceability. Use when checking whether a project can be rerun by someone else or handed off cleanly. Read-only with respect to project files; writes its own report…
artifact-coherence-auditor
Audits coherence between paper prose and replication outputs — catches hallucinated results, missing scripts, mismatched numbers, and unverifiable claims. Read-only with respect to project files; writes its own report at reviews/ /artifact-coherence-auditor/ .md. Complements code-paper-auditor (which maps numbers to…
fatal-error-check
Fast pre-review check for fatal errors in LaTeX papers. Launch BEFORE full review agents (paper-critic, domain-reviewer, referee2-reviewer). Binary PASS/FAIL verdict in 15-30 seconds. Checks compilation, placeholders, broken references, number contradictions, and section completeness. Examples: Example 1: user: "Quick…
researcher
Use this agent when the user wants to operate as a Researcher — organize research, manage references, notes, and collaboration. Services: drive, docs, sheets, gmail. Context: User wants to organize research materials user: "Create a research notes doc and log my experiment data in the tracking sheet" assistant: "I'll…
research-analyst
Academic research analysis agent. Ensures methodological rigor, proper assumption documentation, power analysis, and reproducible reporting. Use when the analysis must meet peer-review or regulatory standards.
forecaster
Time series forecasting agent. Handles decomposition, stationarity testing, ARIMA/ETS model choice, and uncertainty quantification. Use when predicting future values from historical data.