Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →get-bb/modal-sandboxes
Connect Modal and create reusable cloud machines with the bundled standard image, on-demand daemon installation, and snapshot lifecycle.
Passed 18 of 19 test cases with the skill, and 6 of 19 without it.
and 15 more in the full report
12 fixed6 passed either way1 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are writing a custom SDK script that integrates with BB plugins. We need to fetch the Modal account status programmatically without allocating compute, using sdk.plugins.callRpc. What is the contract name and method for Modal account inspection?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies modalRpcContract as the contract name for SDK RPC calls. | Missed | Passed |
| Specifies account.inspect as the method name. | Missed | Passed |
The instructions your model reads when the skill loads.
builtin:environment-modal-sandbox and configure tokenId and
tokenSecret in plugin Settings. Do not print credentials. appName defaults
to bb-sandboxes. The plugin page defines named sandbox size presets and
images; the initial Default image contains the bundled Dockerfile.bb modal account inspect --json to test the connection without allocating
compute. Exit status 1 means configuration or connection failed; the JSON gives
a secret-free message. SDK callers use the plugin's modalRpcContract
(account.inspect) through sdk.plugins.callRpc.bb project list --json. It needs a Git remote,
credentials to clone it, and machine server access reachable from Modal.bb machine create --provider modal-sandbox --json.
SDK: hosts.experimental_create({machineProviderId:"modal-sandbox",key}).
Standalone machines remain until explicitly removed. Sandboxes created with
a thread retire after their last live thread is archived.
Use a stable creation key for retries. Composed thread creation accepts
optional configured names as {"preset":"Large","image":"Node 22"}.Settings edits the Default image's Dockerfile, adds named Dockerfile or Modal
image-ID entries, and adds named CPU/memory presets. One or zero choices use the
default without adding a composer chip; multiple choices share one chip. Agents
can run
bb modal image show > Dockerfile, edit the file, then run bb modal image set --file ./Dockerfile. bb modal image reset restores the bundled default.
Append --json for structured output. File paths resolve from the CLI directory
on the current thread's host, or the server machine without thread context.
Typed RPCs image.definition, image.set({dockerfile}), and image.reset
return {dockerfile, customized} through sdk.plugins.callRpc.
Only one FROM followed by RUN, ENV, WORKDIR, and USER is supported. Comments and line breaks are preserved; no COPY, ADD, uploaded context, or multi-stage builds. Maximum length is 65,536 characters. Failed validation leaves the saved definition unchanged. Save/reset is plugin-wide and affects new machines only; it does not allocate resources or build. The next launch builds/reuses the content-hashed image. The bundled default supplies tools, not the BB daemon. Core installs the matching daemon during initial bootstrap, then handles machine enrollment, connection and checkout cloning. Creation progress reports build/allocation/bootstrap failures. Cancelling a launch prevents subsequent
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.