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 AndyZhuang/Opentest --skill reproducibility-checklistgit clone --depth 1 https://github.com/AndyZhuang/OpentestWrote 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/andyzhuang/opentest/reproducibility-checklist)<a href="https://agentmods.dev/skills/andyzhuang/opentest/reproducibility-checklist"><img src="https://agentmods.dev/badge/skills/andyzhuang/opentest/reproducibility-checklist/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/andyzhuang/opentest/reproducibility-checklist"><img src="https://agentmods.dev/badge/skills/andyzhuang/opentest/reproducibility-checklist.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.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
reproducibility-checklist 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.
This is a copy
100% identical to reproducibility-checklist — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Reproducibility Checklist — Open Science Best Practices
Overview
Ensure research is reproducible, transparent, and meets open science standards.
Pre-Registration
- Study registered on ClinicalTrials.gov, OSF, or AsPredicted before data collection
- Primary outcome and analysis plan pre-specified
- Deviations from pre-registration documented and justified
Data Availability
- Raw data deposited in domain repository (GEO, PDB, PRIDE, Zenodo, Dryad, Figshare)
- Data dictionary/codebook provided
- Sensitive data: de-identification method documented, access controls described
- DOI assigned to dataset
Code Availability
- Analysis code in public repository (GitHub, GitLab, Zenodo)
- Environment specification (requirements.txt, conda env, Docker, renv.lock)
- Random seeds fixed and documented
- README with reproduction instructions
Materials
- Reagent catalog numbers, lot numbers, manufacturer
- Custom materials: synthesis protocol or request process
- Cell lines: STR authentication, mycoplasma testing
- Antibodies: RRID or Antibody Registry ID
Statistical Reporting
- All statistical tests, parameters, and software versions reported
- Effect sizes and confidence intervals (not just p-values)
- Multiple comparison correction method stated
- Sample size justification (power analysis)
Reporting Standards
- Applicable guideline followed (STROBE/CONSORT/PRISMA/ARRIVE/MIQE)
- Checklist completed and submitted with manuscript
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 · 38 lines · 0 tokens per session scan A 1098ea460632
reproducibility-checklist is a skill published in the GitHub repository AndyZhuang/Opentest (22 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 349 tokens. A static security scan graded it A with 0 findings. It is 100% identical to reproducibility-checklist, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
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…