remote-compute-modal
Run GPU jobs on the user's own Modal account via host.compute.create('byoc:modal', ...). Covers the create→submit→wait_for_notification flow, the compute_provider kernel for env setup, image/volume resolution, and the two approval cards. Load once you've decided to dispatch to Modal.
npx skills add BioTender-max/awesome-bio-agent-skills --skill remote-compute-modal --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You're dispatching to the user's Modal account: containers spin up in Modal's cloud, on hardware you name in plain terms (gpu/cpu/memory/timeout), under their workspace, on their bill. That's the reason there are two approval cards rather than one, and the reason the env-setup surface is a separate kernel rather than something you can call inline from the control-plane kernel: each card is the user consenting to a specific, bounded use of their credential, and the architecture keeps those grants legible by keeping the surfaces apart. If `compute.create('byoc:modal', …)` returns `unknown provider 'byoc:modal'`, Modal isn't enabled in this install — ask the user to enable it under *Settings → Compute → Modal* (or surface the prompt; you can't enable it for them). For first-time environment setup, see `env-setup.md` in this skill directory — it walks through driving the `compute_provider` kernel to build and record images. ## Two timeouts, one timeline Modal has two deadline timers. Both live INSIDE the sandbox, and neither can cost you the outputs of a job that ran. The timeline every job runs on: 1. Container life starts at sandbox creation — staging the inputs counts against it, so
- Two timeouts, one timeline
- Two surfaces, one provider
- Workflow
- The image-reference rule
- What latency to expect
- When the user gives you a budget
- Warm reuse, reattachment, and close()
- When the job fails
- What to record
- GPU tier reference
- Volumes
- Modal Environment (Settings → Compute → modal → Environment)
- Which Environment and App am I in?
- Network egress from the job sandbox
What does the remote-compute-modal skill do?
Run GPU jobs on the user's own Modal account via host.compute.create('byoc:modal', ...). Covers the create→submit→wait_for_notification flow, the compute_provider kernel for env setup, image/volume resolution, and the two approval cards. Load once you've decided to dispatch to Modal.
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill remote-compute-modal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.