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/learning-bayesian-statistics/baygent-skills/bayesian-workflownpx skills add Learning-Bayesian-Statistics/baygent-skills --skill bayesian-workflowgit clone --depth 1 https://github.com/Learning-Bayesian-Statistics/baygent-skillsWrote 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/learning-bayesian-statistics/baygent-skills/bayesian-workflow)<a href="https://agentmods.dev/skills/learning-bayesian-statistics/baygent-skills/bayesian-workflow"><img src="https://agentmods.dev/badge/skills/learning-bayesian-statistics/baygent-skills/bayesian-workflow.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.00195 | $0.04661 |
| Opus 5 | $0.00097 | $0.02330 |
| Sonnet 5 | $0.00039 | $0.00932 |
| Haiku 4.5 | $0.00019 | $0.00466 |
Grade A, and why
bayesian-workflow 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 today.
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bayesian Workflow
Workflow overview
Every Bayesian analysis follows this sequence. Do not skip steps -- especially model criticism.
- Formulate — Define the generative story. What underlying process, that we're precisely trying to model, created the data?
- Specify priors — See references/priors.md
- Implement in PyMC — Write the model. Prefer PyMC 5+ syntax. Use the latest version possible.
- Run prior predictive checks —
pm.sample_prior_predictive(). Verify priors produce plausible data ranges before fitting - Inference —
pm.sample(nuts_sampler="nutpie"). Always use nutpie for speed (the nutpie python package provides cutting-edge sampling). Don't hardcode the number of chains — let the sampler pick the best default for the platform. - Diagnose convergence — Use
arviz_stats.diagnose(idata)as the first check (requires arviz-stats >= 1.0.0). It covers R-hat, ESS, divergences, tree depth, and E-BFMI in one call. See references/diagnostics.md - Criticize the model — See references/model-criticism.md
- Check prior sensitivity — Run
psense_summary(idata)to verify conclusions are robust to prior choices. Visualize withplot_psense_dist(idata)fromarviz_plots. Requireslog_likelihoodandlog_priorin the InferenceData — compute them after sampling if needed. See references/sensitivity.md - Compare models (if applicable) — See references/model-comparison.md
- Report results — Generate
<slug>/report.mdusing the canonical template in references/reporting.md. Runscripts/check_diagnostics.pyto turn raw diagnostics into qualitative ratings + an ordered next-steps list, and use that output to fill the Assessment lines and Suggested Next Steps section. When the user mentions a non-technical audience or is new to Bayesian stats, additionally adapt the prose to plain language and include a glossary — but keep the canonical report structure as the audit trail.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- main.py 95 B runs code
- pyproject.toml 181 B
- README.md 4.7 KB
- references/diagnostics.md 8.2 KB
- references/hierarchical.md 7.8 KB
- references/model-comparison.md 4.4 KB
- references/model-criticism.md 12 KB
- references/priors.md 7.9 KB
- references/reporting.md 21 KB
- references/sensitivity.md 4.5 KB
- scripts/calibration_check.py 11 KB runs code
- scripts/check_diagnostics.py 18 KB runs code
- scripts/diagnose_model.py 13 KB runs code
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.
- today Changed · +195 tokens per session f33a8cef9154
- 5d ago First seen · 205 lines · 0 tokens per session scan A 0f2b7d067da9
bayesian-workflow is a skill published in the GitHub repository Learning-Bayesian-Statistics/baygent-skills (172 stars, last pushed yesterday), licensed MIT. It adds 195 tokens to every session and 4,661 once invoked, about $0.0010 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
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…