Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/001TMF/blatant-whynpx agentmods add skills/001tmf/blatant-why/by-experiment-resultsWrote 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/001tmf/blatant-why/by-experiment-results)<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-experiment-results"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-experiment-results/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/001tmf/blatant-why/by-experiment-results"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-experiment-results.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00004 | $0.07479 |
| Opus 5 | $0.00002 | $0.03740 |
| Sonnet 5 | $0.00001 | $0.01496 |
| Haiku 4.5 | $0.00000 | $0.00748 |
Grade A, and why
by-experiment-results 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 11d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Experiment Results Skill
A design campaign only learns when lab outcomes are joined back to the in-silico predictions that produced them. This skill is the wet-lab feedback loop closer: it ingests lab readouts (Adaptyv batch CSVs, internal ELISA plate-reader output, BLI/Octet kinetics, expression QC), joins them to the per-design feature table the screener emitted, and runs a calibration analysis that asks one question for every in-silico feature:
Did this feature actually predict whether the design worked in the lab?
The answer for each feature is one of: validated (in-silico PASS correlated with lab PASS), contradicted (predictor pointed the opposite direction), or inconclusive (no signal). The diagnosis goes into the knowledge graph with that confidence label so future campaigns start from real-world-calibrated priors, not silicon-only priors.
This skill sits between by-screening (which produces in-silico PASS/FAIL) and by-campaign-optimizer (which trains the next round). It is the only skill in BY that consumes ground-truth lab data.
When to Use This Skill
✅ Use this skill when:
- A lab readout file (CSV or Excel) has arrived from Adaptyv Bio for a previously submitted batch
- An internal ELISA, BLI, or Octet run has produced a tidy results table for designs the BY pipeline scored
- You need to validate round-N in-silico predictions against round-N-1 lab outcomes
- A user asks "did our predictions hold up?", "calibrate the screener", or "did ipSAE correlate with Kd?"
- A round of designs has come back from the lab and you need to update the campaign-optimizer training data with ground truth
- You want to write a calibration report showing precision at top-K and lift over random
- You want to publish findings to the knowledge graph as validated or contradicted with confidence levels
❌ Don't use this skill for:
- A campaign that has not yet been submitted to lab — there is no ground truth to compare. Use by-screening + by-failure-diagnosis first.
- Pre-submission ranking of designs — that is by-screening and by-design-workflow.
- Computing raw in-silico scores from PDB / NPZ — use by-scoring.
- Diagnosing why a campaign produced low in-silico pass rate — use by-failure-diagnosis (no lab data needed).
- Lab submission itself — use the gated
/by:approve-labflow and by-adaptyv MCP tools. - Curating raw structural files (CIF / PDB) — those stay in the campaign directory.
What ships with it
6 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.
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.
- 11d ago First seen · 427 lines · 4 tokens per session scan A c23d9971fc9e
by-experiment-results is a skill published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 25d ago), licensed MIT. It adds 4 tokens to every session and 7,479 once invoked, about $0.0000 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
statistical-modeling
Statistical modeling and machine learning for biomarker discovery, survival analysis, classification, regression, and model interpretation.
chromatin-regulation
Chromatin regulation analysis from called peaks and count matrices — differential binding, signal summarisation, peak annotation, and scATAC-seq.
genomic-variants
Analysis of called genomic variants — filtering, annotation, GWAS, and population-genetics summaries from VCF and PLINK-format data.
bulk-transcriptomics
Bulk RNA-seq and microarray differential expression analysis including method selection, batch correction, and complex experimental designs.
spatial-omics
Spatial transcriptomics and spatial proteomics analysis covering technology-specific workflows, spatial statistics, deconvolution, and niche analysis.
drug-repurposing
Systematic drug repurposing via signature matching, target-based analysis, network proximity, genetic evidence scoring, and clinical evidence mining.