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 skills/wentorai/research-plugins/hypothesis-testing-guidenpx skills add wentorai/research-plugins --skill hypothesis-testing-guidegit clone --depth 1 https://github.com/wentorai/research-pluginsWrote 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/wentorai/research-plugins/hypothesis-testing-guide)<a href="https://agentmods.dev/skills/wentorai/research-plugins/hypothesis-testing-guide"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/hypothesis-testing-guide.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.00016 | $0.02167 |
| Opus 5 | $0.00008 | $0.01084 |
| Sonnet 5 | $0.00003 | $0.00433 |
| Haiku 4.5 | $0.00002 | $0.00217 |
Grade A, and why
hypothesis-testing-guide 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- research-hypothesis-testing — 89% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hypothesis Testing Guide
Overview
Hypothesis testing is the backbone of empirical research. It provides a principled framework for deciding whether observed differences in data reflect genuine effects or merely random variation. Misuse of hypothesis tests -- p-hacking, ignoring assumptions, confusing statistical and practical significance -- is a leading cause of irreproducible findings.
This guide covers the core hypothesis testing framework, the most commonly used tests across disciplines, assumption checking, effect size reporting, power analysis for sample size planning, and multiple comparison corrections. Each test is accompanied by Python code using scipy, statsmodels, and pingouin, ready to integrate into research workflows.
The goal is not just to help you run tests, but to help you run the right test correctly and report results following modern standards (APA 7th edition, journal best practices).
The Hypothesis Testing Framework
Step-by-Step Procedure
- State hypotheses. Define H0 (null: no effect) and H1 (alternative: effect exists).
- Choose significance level. Typically alpha = 0.05, but justify your choice.
- Select the appropriate test. Based on data type, distribution, and design.
- Check assumptions. Normality, homogeneity of variance, independence.
- Compute test statistic and p-value.
- Report effect size and confidence interval. p-values alone are insufficient.
- Make a decision. Reject or fail to reject H0, with practical interpretation.
Common Errors
| Error Type | Definition | Probability |
|---|---|---|
| Type I (False Positive) | Reject H0 when it is true | alpha (usually 0.05) |
| Type II (False Negative) | Fail to reject H0 when it is false | beta (usually 0.20) |
| Power | Probability of correctly detecting an effect | 1 - beta (target: 0.80) |
Test Selection Guide
| Research Question | Data Type | Groups | Test |
|---|---|---|---|
| Two group means differ? | Continuous, normal | 2 independent | Independent t-test |
| Before/after difference? | Continuous, normal | 2 paired | Paired t-test |
| Multiple group means differ? | Continuous, normal | 3+ independent | One-way ANOVA |
| Two group medians differ? | Ordinal / non-normal | 2 independent | Mann-Whitney U |
| Before/after (non-normal)? | Ordinal / non-normal | 2 paired | Wilcoxon signed-rank |
| Multiple groups (non-normal)? | Ordinal / non-normal | 3+ independent | Kruskal-Wallis |
| Association between categories? | Categorical | 2 variables | Chi-square test |
| Correlation? | Continuous | 2 variables | Pearson or Spearman |
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.
- 4d ago First seen · 211 lines · 16 tokens per session scan A 95c1dc213434
hypothesis-testing-guide is a skill published in the GitHub repository wentorai/research-plugins (285 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 2,167 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…