Update to Biohub ESM

{
  "name": "esmfold2-binder-design",
  "description": "Use when the user needs ESMFold2 inversion for minibinder, binder, or scFv campaigns, Modal scale-out, candidate selection, persistence, or private self-hosting. Never route to Biohub managed API; not for ordinary folding or single-seed efficacy claims.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    },
    {
      "relative_path": "references/campaign.md",
      "size_in_bytes": 2128
    },
    {
      "relative_path": "references/modal.md",
      "size_in_bytes": 7380
    }
  ],
  "skill_md_contents": "---\nname: esmfold2-binder-design\ndescription: Use when the user needs ESMFold2 inversion for minibinder, binder, or scFv campaigns, Modal scale-out, candidate selection, persistence, or private self-hosting. Never route to Biohub managed API; not for ordinary folding or single-seed efficacy claims.\n---\n\n# ESMFold2 binder design\n\nBinder design is not available through the Biohub managed API today. Route only to the released open-weight workflow on Modal or suitable user-owned compute. Modal public-weight execution needs Modal authentication, not `ESM_API_KEY`.\n\n## Campaign contract\n\n1. Validate target sequence/structure, binder modality (minibinder or scFv), templates, constraints, and biosafety/AUP fit.\n2. Pin `Biohub/esm`, ESMFold2/ESMC weights, helper code, and every seed.\n3. Explain scale honestly: useful campaigns normally need hundreds and often about 1,000 designs across seeds/templates. A one-seed smoke test verifies integration only and is not representative screening depth or efficacy.\n4. Set explicit candidate-count, GPU, timeout, persistence, and concurrency bounds in the pinned campaign contract. Refresh current provider pricing and payment readiness, show the scope and a cost ceiling, and obtain separate explicit current-turn confirmation before material GPU spend.\n5. Only after that confirmation, spawn no more than the confirmed job count, persist every call ID immediately, gather with partial-failure handling, and support cancellation/resume. A runtime `--confirm-cost` flag records the confirmed boundary; it never creates consent by itself.\n6. Preserve sequences, trajectories, structures, raw metrics, selection table, exact critic configuration, and provenance. Do not select on one metric alone or claim affinity from structural confidence.\n7. Require experimental screening and appropriate safety review before any biological conclusion.\n\nThe official Modal example uses an H100, persistent model/results Volumes, `spawn()` plus `FunctionCall.gather`, deterministic algorithms, and a server-side selection pass. The model plus four critic models are roughly 50 GB. A bounded live smoke uses exactly one seed and batch size one.\n\nRead [Modal execution](references/modal.md), [campaign design and interpretation](references/campaign.md), and shared [safety/provenance](../../references/safety-and-provenance.md).\n"
}