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/poplarity/dsh-science-workbenchnpx agentmods add skills/poplarity/dsh-science-workbench/bio-workbenchWrote 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/poplarity/dsh-science-workbench/bio-workbench)<a href="https://agentmods.dev/skills/poplarity/dsh-science-workbench/bio-workbench"><img src="https://agentmods.dev/badge/skills/poplarity/dsh-science-workbench/bio-workbench/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/poplarity/dsh-science-workbench/bio-workbench"><img src="https://agentmods.dev/badge/skills/poplarity/dsh-science-workbench/bio-workbench.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.00147 | $0.04067 |
| Opus 5.5 | $0.00059 | $0.01627 |
| Sonnet 5.5 | $0.00029 | $0.00813 |
| Haiku 4.5 | $0.00015 | $0.00407 |
Grade A, and why
bio-workbench 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.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生信分析工作台约定(dsh-science-workbench)
这是 agent 在执行生信分析时必须遵守的约定。核心原则:每个产物都可溯源、可重放——回答"这张图 = 哪段代码 + 哪些输入 + 什么环境 + 什么参数/种子",并能重跑。
1. 项目布局
每个分析项目是一个目录,结构固定:
<workspace>/bio-projects/<name>/
├─ manifest.json # 唯一事实来源(账本):cells + artifacts + provenance + 反馈
├─ environment.lock # 环境快照(interpreter 版本 + pip freeze)
├─ code/ # 每个 cell 一个自包含脚本 cell_0001.py / cell_0001_v2.py ...
├─ data/ # 输入数据(引用或副本)
├─ figures/ # 只放图:.svg / .pdf / .tiff / .png
├─ results/ # 非图产物:tsv/csv/bed/npz + source data
└─ .git/ # 项目自动 git(每次 cell 跑完/反馈 自动本地 commit,不 push)
项目里不保留 QA 产物。 审计(alignment / collision)必须照跑,但它们的产物是 scratch: alignment overlay 是测量示意图(每个可比面板一个矩形 + PASS 页脚),collision overlay 标的是 可疑的文字/描边碰撞。两者都不是图,摆在项目里就是污染分析结果,还会招来误解点击。 一律写到项目外的临时目录,例如:
import os, tempfile
QADIR = os.path.join(tempfile.gettempdir(), 'nature-figure-qa',
os.path.basename(os.path.abspath('.'))) # cwd = 项目根
os.makedirs(QADIR, exist_ok=True)
print(f'QA scratch dir (outside the project): {QADIR}')
并且绝不把 QA 文件写进 outputs 声明。踩过的坑:collision 审计在 0 冲突时不写 overlay PDF,
但 outputs 里仍列着那个路径,于是账本里留下一条文件不存在的幽灵 artifact,在 UI 里点开就是空的。
2. cell 契约(脚本头声明块)
每个 cell 脚本顶部有一段由工具生成的声明头,声明即契约:
# @cell: cell_0001
# @title: TSS profile
# @language: python
# @seed: 42
# @params: {"bin": 50, "upstream": 3000}
# @inputs: ["data/peaks.bed"]
# @outputs: ["figures/tss_profile.png"]
规则:
- 图必须写到
figures/下(相对项目根路径),这样运行后能自动被发现并登记 provenance。 - 审计产物写到项目外的临时目录,绝不写进项目(见 §1)。
figures/被自动扫描并在 UI 里当图展示;alignment overlay 每面板一个矩形 + PASS 页脚,放进去会被误认成坏图。 - QA 路径不要出现在
outputs里,否则会留下文件不存在的幽灵 artifact。 - 非图的中间产物(tsv/csv/bed 等)通过
outputs显式声明,放results/。 - 脚本要自包含:显式读输入、写输出;cwd = 项目根;用相对路径。
3. manifest 记账(唯一事实来源)
{
"schemaVersion": 1,
"name": "...", "root": "...",
"environment": {"language": "python", "interpreter": "3.12.x", "lockFile": "environment.lock"},
"cells": [ { "id", "title", "script", "language", "params", "seed", "inputs",
"status": "ok|error", "artifacts": [], "ranAt", "stdoutTail", "stderrTail", "derivedFrom" } ],
"artifacts": [ { "path", "kind": "figure|data|file", "producedBy", "inputHashes",
"outputHash", "params", "seed", "env", "createdAt", "feedback": [], "derivedFrom" } ]
}
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 Changed · +105 lines · +31 tokens per session 120e4fa9b6c4
- 1mo ago First seen · 96 lines · 116 tokens per session scan A 2c3254267fa2
bio-workbench is a skill published in the GitHub repository poplarity/dsh-science-workbench (11 stars, last pushed 9d ago), licensed MIT. It adds 147 tokens to every session and 4,067 once invoked, about $0.0006 per session on Opus 5.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-31.
Other skills, from other repositories
structure-prediction
Protein structure prediction from sequence. ESMFold-based, single GPU, no MSA needed. Predicts 3D structures with pLDDT confidence scores for drug discovery targets.
ito-compute
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately installed canonical CLI. Use when a user asks to find H100/H200 capacity, request a fixed compute rate, check Itô…
ito-inference
Inspect the availability of model serving on a completed Itô compute booking and, when the canonical backend becomes available, hand off an explicitly confirmed serving manifest. Use after ito-compute has booked GPU nodes and the user asks for an OpenAI-compatible endpoint, ito-serve, hosted Kimi, or self-hosted…
ito-training
Inspect the availability of ML training on a completed Itô compute booking and, when the canonical backend becomes available, hand off an explicitly confirmed training manifest. Use after ito-compute has booked GPU nodes and the user wants pre-training, fine-tuning, or RL on that metal. ECC implements no training…
Jupyter Live Kernel
Guides notebook-first analysis with reproducible kernels, inspectable data loading, and explicit promotion paths back into durable code.
ehr-analysis
End-to-end EHR predictive modeling pipeline with PyHealth, covering dataset loading, task definition, model training, evaluation, calibration, and clinical interpretation.