Biohub ESM
Chan Zuckerberg Biohub, Inc. v0.2.4
Understand proteins with ESM
From the developer
Listing not observed in the last 24 hours. Check collection status.
Declared capabilities
- Interactive
- Read
- Write
Not specified in the available declarations: limitations, pricing & account requirements.
Onboarding example
Map the mutational landscape of PETase and show me where it is most constrained or tolerant.
Sources & dates
Developer declarations; not independently tested. Listing last checked Oct 5, 2026. Package observed Oct 5, 2026.
Description
From the marketplace listing
Biohub ESM helps you understand proteins from a name, sequence, or file: explore mutation landscapes, interpret what ESMC sees, predict and view all-atom structures, and discover related proteins. It chooses the right ESM workflow, preserves confidence and provenance, and presents results automatically. It also supports MSA-guided and modified-complex workflows, binder planning, and private or large-scale compute routing.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Sep 30, 2026. Last seen Oct 5, 2026.
Similar plugins
Finding similar plugins… Results will appear here automatically.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
biohub-esm7.45 KB
--- name: biohub-esm description: Route Biohub ESM requests to ESMC, ESMFold2, ESM Atlas, Modal, or private open weights. Use for explicitly ESM/Biohub work, ESM protein representations or mutation scoring, ESMFold2 folding, Atlas discovery, ESM binder design, or choosing an ESM compute route. Do not use for unrelated non-ESM models, generic sequence alignment, or standalone structure viewing unless the user explicitly asks to compare it with Biohub ESM. --- # Biohub ESM router Use this as the implicit entry point. Identify the scientific goal before choosing a model or provider; ESMC, ESMFold2, and Atlas are different artifacts. ## Route first | User need | Default | Escalation | | --- | --- | --- | | Existing-protein discovery, functional neighborhoods, Atlas feature catalog, clusters | public Atlas alpha API | anonymous Atlas S3 for bulk data | | SAE activation extraction or interpretation for an input sequence | Biohub managed ESMC | pinned ESMC weights for private or custom work | | Public ESMC inference, including bounded concurrent calls | Biohub managed API | self-host for private, custom, sustained, or owned-compute work | | One or modest structure predictions | Biohub managed ESMFold2 | full + MSA for difficult targets; Modal for bulk | | Many independent folds or sweeps | Modal open weights | user-owned GPUs | | Minibinder, binder, or scFv design | Modal or self-hosted open weights | never Biohub managed API until documented | | Private, offline, air-gapped, data-resident, customized, fine-tuned, sustained | Hugging Face weights on user-owned compute | user owns capacity and operations | Run the deterministic router when the route is not already explicit: ```bash python3 <plugin-root>/scripts/biohub_esm.py route --task fold --item-count 500 ``` The 32-item scale-out threshold applies to folding. It is a planning heuristic, not a Biohub account quota. Public ESMC calls stay on the managed API; the plugin ships no ESMC Modal function. Do not hardcode account-specific capacity limits. ## Natural starter experiences Treat the plugin page's exact prompts as outcome-rich launchers into the official tutorial contracts in `../../examples/tutorial-use-cases.json`: - `Map the mutational landscape of PETase and show me where it is most constrained or tolerant.` - `Show me what ESMC has learned about ATP synthase and map the strongest features onto its structure.` - `Model how a modified GLP-1 peptide with a lipid linker might engage GLP-1R, then show me the complex.` Resolve their hidden scientific inputs, select the specialist and model, produce the tutorial-shaped analysis, and present the visual result without making the user translate the request into sequences or SDK objects. The focused GB1 regression launchers in `../../examples/starter-examples.json` remain supported: - `What might W43F do to GB1?` - `Show me what GB1 looks like.` - `Find proteins similar to GB1.` The three exact plugin-page prompts are curated official-tutorial launchers. Before adopting their pinned target or construct, disclose its exact identity together with the execution route, model, item and call counts, parameters, artifact plan, and available cost information. The PETase prompt authorizes only its disclosed exact 259-request managed runtime once access is configured. The ATP-synthase and GLP-1R prompts do not authorize provider calls; obtain separate explicit current-turn confirmation for their disclosed exact calls. No prompt authorizes a substituted target, a different request scope, or Modal, self-hosted, or bulk-transfer work. An explicit planning-only or no-network request overrides execution. Outside those three exact prompts, resolve a bundled literal only for an explicitly named tutorial example. A generic target request, or a prompt that says “my A3M/MSA,” must use the user's supplied biological input or pause for the missing input; never substitute a tutorial fixture. The 259-context PETase landscape runs on the managed
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
biohub-esm-setup9.01 KB
--- name: biohub-esm-setup description: Set up and preflight Biohub ESM, Atlas, Modal, and Hugging Face access. Use when installing pinned ESM dependencies, checking credentials, or fixing auth, rate-limit, credits, PATH, SDK, or GPU setup. Never ask for secret values. --- # Biohub ESM setup and auth ## No key yet When `biohub_managed.status` is `missing`, inspect `esm_sdk_runtime` before starting credential setup. If the selected managed workflow imports the pinned `esm` SDK and `esm_sdk_runtime.status` is `unsupported`, report both blockers in the same handoff: say that the workflow requires Python 3.12, and quote the reported interpreter and remedy. This applies to managed ESMC mutation scoring, `esmc-landscape`, and ESMFold2 response serialization. Do not wait until after the key is configured to reveal the Python blocker. When no verified host credential action is available, use this credential instruction alongside the Python blocker when applicable: > Get a free API key at <https://biohub.ai/developer-console/api-keys> (existing Forge accounts can sign in), set it as `ESM_API_KEY` in the environment that launches Codex, then restart Codex. Preflight returns `obtain_key_url`, `variable`, and `esm_sdk_runtime` alongside the status, so quote those rather than composing your own setup requirements. If a verified credential action is available, follow **Seamless credential recovery** below instead. Apart from current setup blockers, do not describe routes, models, request counts, or costs before the key exists — none of it is actionable yet. Once the key and runtime are configured, resume the original request automatically without asking the user to repeat it. ## Safe preflight The agent runs the base status-only check directly for credentials, Atlas, and routes that do not materialize a managed structure: ```bash python3 <plugin-root>/scripts/biohub_esm.py preflight ``` For a managed fold, run the selected endpoint's capability preflight with the same provisioned Python 3.12 interpreter that will execute the request: ```bash <python-3.12-with-pinned-esm> <plugin-root>/scripts/biohub_esm.py preflight --endpoint fold <python-3.12-with-pinned-esm> <plugin-root>/scripts/biohub_esm.py preflight --endpoint fold_all_atom ``` Run only the applicable endpoint command. Its `managed_structure_materialization` report verifies the interpreter, exact ESM and Transformers source revisions, endpoint-specific imports, and a tiny offline serialization. A blocked report must stop the workflow before credential access, output creation, or provider submission; apply its bounded remediation and rerun that endpoint preflight. Resolve the placeholder to the provisioned interpreter (`.venv/bin/python` for the install below) and use that exact interpreter for the subsequent managed command. Credential entries report only `configured`, `missing`, `optional-missing`, or `not-required`; `esm_sdk_runtime` separately reports `supported` or `unsupported`. On macOS, preflight probes only whether the recognized Keychain item exists; it never requests the value or uses `security ... -w`. Execution-time resolution may retrieve the existing item only when the selected route is authorized to run: tutorial-scale managed Biohub requests run without a separate confirmation, while Modal, self-hosted, and bulk-transfer routes require the route-specific confirmation first. Do not hand the command to the user when tool execution is available. Never open or display `.modal.toml`; file presence is enough for preflight. ## Seamless credential recovery When managed Biohub access reports `missing`, keep the current request intact while setup completes. 1. Use the host's existing secure credential setup action for `ESM_API_KEY`, when one is actually available. Invoke it once and tell the user the verified host surface where its masked prompt will appear, such as a credential sheet in the app. Never claim that a terminal prompt exists unless the invoked actio
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
esm-atlas7.59 KB
--- name: esm-atlas description: Use when the user needs ESM Atlas similarity search, MD5 protein lookup, structures, clusters, Pfam/taxonomy context, the existing 16,384-feature Atlas SAE catalog, thumbnails, batch jobs, or anonymous S3 data. Use ESMC instead to extract SAE activations for a supplied sequence. Atlas is not a deployable model and currently needs no client key. --- # ESM Atlas Atlas is public data/discovery infrastructure, not another model to run through Modal or Hugging Face. The current `v1alpha1` API needs no client-side key and is explicitly unstable/not recommended for production assumptions. Atlas feature details cover the 16,384-feature catalog for the pinned tutorial's `esmc-6b-2024-12-sae-layer60-k64-codebook16384`. Do not apply them across checkpoints, models, layers, or codebooks. Extract activations with `$esmc`; record normalization separately because it changes scaling and ranking, not feature-index identity. The k64 SAE retains at most 64 positive features per residue. `per_residue_activations` is the complete post-sparsification tensor, not API truncation, although quantization can round small values to zero. For `Find proteins similar to GB1.`, resolve the pinned fixture through `../../examples/starter-examples.json`; do not ask the user to paste the bundled sequence. Make exactly one public similarity-search GET with `topk_results=10`, `topk_features=20`, `min_similarity=0.5`, and `include_cluster_info=true`, writing to `/absolute/path/gb1-atlas-similarity-search`. Return up to ten hits only after validating unique MD5s, non-empty accessions, client-required positive integer lengths, scores in 0–1 and at or above 0.5, and nonincreasing score order. Use only cluster metadata embedded in that search response and make zero protein or cluster-detail follow-ups. Preserve `raw-response.json`, `result.json`, and `provenance.json`; optional `search-<n>.pdb` artifacts exist only for hits with provider-embedded coordinates. Atlas needs no client-side key, so run it directly and do not substitute a model deployment. ## Conservative boundaries - similarity search: raw Atlas accepts 1 to 2,048 sequence characters; the bundled plugin must validate at no more than 800 residues. Never clip; ask for a domain or search labeled windows. - on-demand fold: opt-in only. The partner-inspected backend accepts 1 to 700 sequence characters, while published guidance says <700; the plugin exposes only hash-based fold-on-miss and caps the returned stored sequence at 699 sequence characters. It first performs a non-folding lookup and proceeds only when the actual returned sequence matches the MD5 and plugin-supported alphabet and the record lacks coordinates; `sequence_length` alone or missing sequence evidence is rejected. It cannot fold an unknown hash or caller-supplied sequence; do not bypass it with an ad hoc request. Start with similarity search when the input is a sequence. - feature index: 0–16,383 - batch: at most 500 unique MD5 hashes. The plugin rejects malformed hashes before submission; the raw API instead returns per-protein errors. Only relax a boundary after a live schema/probe is captured and tests are updated. Preserve the raw alpha response before normalization. ## Workflows ```bash # Learned-feature similarity search python3 <plugin-root>/scripts/biohub_esm.py atlas search \ --sequence "$SEQUENCE" --topk-results 10 --include-cluster-info \ --output-dir /absolute/path/atlas-search # Separate opt-in protein and representative-cluster traversal; not part of the canonical starter python3 <plugin-root>/scripts/biohub_esm.py atlas protein \ --protein-hash <md5> --output-dir /absolute/path/protein python3 <plugin-root>/scripts/biohub_esm.py atlas cluster \ --protein-hash <cluster-representative-md5> --output-dir /absolute/path/cluster # Feature catalog/detail with raw response and provenance python3 <plugin-root>/scripts/biohub_esm.py atlas features \ --output-dir /absolute/path/features
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
esmc8.22 KB
--- name: esmc description: Use when the user needs ESMC embeddings, hidden states, logits, entropy, zero-shot mutation scoring, SAE features, fitted heads, or fine-tuning. Sequence only; not for folding, Atlas lookup, or calling an untrained classifier predictive. --- # ESMC ESMC is a sequence-only masked protein language model. Validate the input before inference: ```bash python3 <plugin-root>/scripts/biohub_esm.py validate-sequence \ --target esmc --sequence-file /absolute/path/query.fasta ``` The context is 2,048 tokens. Because current tokenizers add BOS/EOS, the helper uses a conservative 2,046-residue raw-sequence cap unless a pinned tokenizer probe proves a different count. Do not pass structures, DNA, RNA, or ligands. ## Model and route | Route | IDs | | --- | --- | | Biohub managed | `esmc-300m-2024-12`, `esmc-600m-2024-12`, `esmc-6b-2024-12` | | Hugging Face | `biohub/ESMC-300M`, `biohub/ESMC-600M`, `biohub/ESMC-6B` | Default to managed ESMC for public inference, including bounded concurrent calls that the managed backend can auto-batch. The plugin ships no ESMC Modal function. Use pinned Hugging Face weights on user-owned compute for private, offline, custom-head, fine-tuned, sustained, or explicitly owned-compute workloads. ## Analysis contract 1. Preserve the normalized sequence digest and exact model/revision. 2. Request only the outputs needed: sequence logits, per-residue embedding, mean embedding, selected hidden states, or named SAE models. 3. For the default biological residue-entropy metric, mask the evaluated residue, predeclare the allowed residue-token set, exclude special/control tokens, and renormalize over only those residue tokens. Keep full-vocabulary log probabilities separate. When explicitly reproducing the official PETase notebook, report its complete-vocabulary entropy in bits as a separately named tutorial metric with its token set and log base; never relabel it as residue entropy. 4. For zero-shot mutation scoring, report the documented score definition, typically `log P(mutant | masked context) - log P(wild type | masked context)`. Keep raw log probabilities and residue numbering. 5. Treat embeddings and SAE activations as features, not biological labels. 6. A downstream classifier/regressor becomes a prediction only after fitting on appropriate labeled data and validating on held-out, leakage-controlled data. Never run an untrained classification head and name its random output. 7. Record outputs and provenance atomically; large tensors should be files with checksums, not pasted into chat. Biohub's pinned official mutation-landscape and SAE tutorials define two page-facing workflows in `../../examples/tutorial-use-cases.json`: - `Map the mutational landscape of PETase and show me where it is most constrained or tolerant.` is a curated tutorial launcher. Disclose the pinned CaPETase literal before adopting it, run status-only preflight, then execute the exact `runtime.command` from the tutorial contract using the verified Python 3.12 environment; do not recreate the analysis in generated code. The shipped `esmc-landscape --tutorial petase` path validates the literal digest, uses a bounded 16-worker `ThreadPoolExecutor` for all 259 host-pinned managed logits calls, and writes exact-request-bound per-position checkpoints before producing `raw-responses.json`, `mutation-landscape.json`, `mutation-landscape.csv`, and `provenance.json`. If interrupted, use only `runtime.resume_command`; never replay an indeterminate submission. Present its constrained/tolerant summary, separately named full-vocabulary tutorial entropy, genuine-substitution fraction, and canonical-amino-acid LLRs. Do not route this to Modal: the plugin ships no ESMC Modal function. - `Show me what ESMC has learned about ATP synthase and map the strongest features onto its structure.` is a curated launcher for experimental PDB 2XND chain A, using managed `esmc-6b-2024-12` with SAE `esmc-6b-2024-12-sae-layer60-k64-code
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 4 — file references are metadata, not package contents.
esmfold29.08 KB
--- name: esmfold2 description: Use when the user needs ESMFold2 all-atom folding for proteins, DNA, RNA, modified residues, or ligands, including Fast/full routing, MSA, confidence, structures, and provenance. Not for dynamics, experimental truth, Atlas discovery, or binder campaigns. --- # ESMFold2 ## Choose the model | Need | Managed | Hugging Face | | --- | --- | --- | | accuracy, difficult complexes, or optional MSA | `esmfold2-2026-05` | `biohub/ESMFold2` | | fast single-sequence throughput | `esmfold2-fast-2026-05` | `biohub/ESMFold2-Fast` | Fast is not MSA-conditioned. If the user supplies or requires an MSA, route to full ESMFold2 and validate query alignment. Missing MSA is not an error for a single-sequence fold unless the user explicitly required MSA conditioning. For `Show me what GB1 looks like.`, resolve the thin launcher through `../../examples/starter-examples.json`; do not ask the user to paste the bundled sequence. Validate the pinned fixture and exact one-request contract in `../../examples/gb1-esmfold2-fast-fold-request.json`, then run it. Complete `preflight --endpoint fold` with the provisioned Python 3.12 runtime first and any `$biohub-esm-setup` work if access is missing, then execute one managed `POST /api/v1/fold` request with `include_pae=true`, the Fast parameters, and the `prediction.pdb`, `presentation-request.json`, `result.json`, `raw-response.json`, and `provenance.json` outputs. A single managed fold at this scale needs no confirmation. Managed requests may incur cost. Report provider-returned credit or token usage when available; otherwise state that the API did not report usage or cost, and never invent an estimate. Continue through local artifact recovery without repeating the provider request. Also recognize the official-tutorial-shaped launchers in `../../examples/tutorial-use-cases.json`: an RNase H1–RNA/DNA hybrid, ubiquitin with a user-supplied A3M, a modified peptide–receptor complex with a covalent linker, and an antibody–antigen complex with user-supplied paired A3Ms. The exact plugin-page launcher `Model how a modified GLP-1 peptide with a lipid linker might engage GLP-1R, then show me the complex.` may resolve the pinned tutorial construct only after disclosing the tagged receptor construct, representative non-therapeutic linker, chemistry, covalent indices, route, model, request count, artifacts, and available cost information in the frozen plan. This tutorial contract does not authorize a provider call; obtain separate explicit current-turn confirmation for that exact fold. Outside that exact launcher or an explicitly named tutorial example, retain the user's sequences/MSAs or pause for missing biological input; never silently substitute the tutorial target. Modal and self-hosted GPU work also requires a frozen scope, cost ceiling, and plain yes/no confirmation. Present a successful structure by default without making the user translate the request into SDK objects, and lead with the structure rather than with a description of what you are about to do. ## Recover an accepted response Use recovery only when a saved response proves the provider accepted and returned the request but local conversion or materialization failed. It makes zero provider calls. Never use it for an indeterminate submission, and always choose a new output directory that does not exist. ```bash <python-3.12-with-pinned-esm> <plugin-root>/scripts/biohub_esm.py managed-recover \ --endpoint fold_all_atom \ --input /absolute/path/frozen-request.json \ --raw-response /absolute/path/raw-response.json \ [--source-provenance /absolute/path/provenance.json] \ --output-dir /absolute/path/new-recovery-output ``` Use `--endpoint fold` for a saved sequence-fold response. Omit `--source-provenance` only when no matching incomplete provenance exists. Consume the new directory's validated `presentation-request.json` exactly; it retains the artifact identity and `openIntentId` for the presentation hando
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 4 — file references are metadata, not package contents.
esmfold2-binder-design2.3 KB
--- 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. --- # ESMFold2 binder design Binder 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`. ## Campaign contract 1. Validate target sequence/structure, binder modality (minibinder or scFv), templates, constraints, and biosafety/AUP fit. 2. Pin `Biohub/esm`, ESMFold2/ESMC weights, helper code, and every seed. 3. 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. 4. 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. 5. 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. 6. 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. 7. Require experimental screening and appropriate safety review before any biological conclusion. The 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. Read [Modal execution](references/modal.md), [campaign design and interpretation](references/campaign.md), and shared [safety/provenance](../../references/safety-and-provenance.md).
Referenced files: 3 — file references are metadata, not package contents.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- Chan Zuckerberg Biohub, Inc.
- Keywords
- See keywords
Declared capabilities
- Interactive
- Read
- Write
Package observed Oct 5, 2026.
Technical details
- First seen
- Sep 30, 2026 · 22:02 UTC
- Last seen
- Oct 5, 2026 · 18:00 UTC
- Collection status
- Collected
plugins_6a820fc4552c819199199afae3bbee0a
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.