Menu

Individual skill

setup-openfold3_ob0-remote-tool

0upvotes

Set up, launch, validate, and troubleshoot the OpenFold3 OpenBind-0 ToolUniverse remote tool and optionally relay it through ToolUniverse Connect. Use when deploying or auditing this implementation.

skills/setup-openfold3_ob0-remote-tool/SKILL.md

Read pinned source

Source commit 5598a9fc97e32964fe9b703818e7d0747142f179

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
1,780
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Set up OpenFold3 (OpenBind-0) as a remote tool

> Validation status (2026-10-01): OpenFold3 0.5.0 with the OpenBind-0 parameters, under the optimization kit's `fast` mode, ran on the NVIDIA GB10 (aarch64, cc 12.1, driver 580.173.02) with `pair_transition` ablated through the kit's own MODEL_OPT_LEVERS_OFF door, the kit's `post_release` gate forced on every item, and the data loader forced to 0 workers. All five `tu remote setup` steps green. Verified on the whole acceptance sequence, not a single smoke: an ascending 100/200/400-residue ladder (3/3), a mixed-shape sequence 100/100/200/100 (4/4), FOUR CONSECUTIVE IDENTICAL REQUESTS (4/4), and three consecutive 800-residue requests (3/3) -- five mmCIF models every time. TWO independent second-request defects had to be fixed first, one in the kit's shared core and one in upstream 0.5.0 itself, and only one of them was findable by repeating a shape. Peak reserved 2.20 GiB at 35 residues rising to 9.97 GiB at 800, which is the declared budget and the ceiling the tool enforces. Wall times were taken with one to three other providers' workers on the card and are not measurements; residency returns 1.25x at 35 residues and 1.13x at the 800-residue budget row against a fresh process per request, because ~30 s of each request is Lightning and featurisation rather than the model. Public publication, cross-user isolation, concurrency, recovery and biological accuracy are untested; keep this deployment private.

## Which OpenFold3 this is

The parameters are **OpenBind-0** (`of3-ob-2025-06-30-174k.pt`, registry name
`openbind-2025-06-30-174k`) and the upstream is **OpenFold3 0.5.0**. The
`openfold3` provider on port 8039 is 0.4.1 with the `of3-p2-155k.pt`
"preview-2" parameters. They are not two configurations of one thing:

- upstream version-gates every checkpoint, and OpenBind-0 declares
  `version_compatibility = ">=0.5.0"` while the preview checkpoints declare
  `">=0.4,<0.4.4dev0"` and are listed in `LEGACY_CHECKPOINTS`, which 0.5.0
Back to top