Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/synthetic-sciences/openscience/vast-ainpx skills add synthetic-sciences/openscience --skill vast-aigit clone --depth 1 https://github.com/synthetic-sciences/openscienceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/synthetic-sciences/openscience/vast-ai)<a href="https://agentmods.dev/skills/synthetic-sciences/openscience/vast-ai"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/vast-ai.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00034 | $0.00721 |
| Opus 5 | $0.00017 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
vast-ai-gpu-cloud scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vast.ai GPU Cloud
Use this skill for Vast.ai marketplace discovery and instance operations. Offers, reliability attributes, locations, bandwidth, storage, and prices are live marketplace data; query them immediately before recommending anything.
OpenScience credential boundary
- A key saved in Customize > Compute > Vast.ai is encrypted control-plane data and is not exported to agent shells, notebooks, kernels, plugins, or MCP servers.
- Use
provider_computewithaccount,list_resources, orresource_statusfor live account and instance reads. OpenScience selects onlyvastai show user --raw,show instances --raw, or one exactshow instance <id> --rawinvocation. - Test connection uses the same boundary for exactly
vastai show user --raw. - The saved key is admitted only when Test connection approves a root/admin-managed, non-writable
vastaiexecutable. A normal user-owned pip, pipx, or Homebrew install remains credential-only and cannot be used byprovider_computeuntil a managed/native adapter exists. last_usedchanges only after that command succeeds.- Never print or persist the key. The saved credential cannot search/accept offers or start, stop, destroy, copy, or change instances; a generic shell needs independent user-managed authentication.
Current CLI contract
vastai --help
vastai show user --raw
vastai show instances --raw
Use vastai --help and the exact subcommand's --help before constructing marketplace filters or mutations. Do not rely on remembered filter fields or create flags.
Marketplace policy
- Confirm GPU memory/count, disk, bandwidth, reliability, verification requirements, location, runtime, interruption tolerance, and maximum budget.
- Query live offers. Preserve the provider's exact offer ID and quoted terms.
- Recommend one offer and explain the material reliability and interruption tradeoffs. Do not optimize on hourly price alone.
- Get explicit approval before accepting an offer, creating or destroying an instance, changing storage, or interrupting a workload.
- After creation, reconcile by instance ID before retrying any ambiguous request.
- Verify SSH and workload health; do not treat an instance state alone as proof the job succeeded.
- Copy and verify required outputs before destruction. Ask separately before deleting durable volumes or templates.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 57 lines · 34 tokens per session scan A a2332d853ddb
vast-ai-gpu-cloud is a skill published in the GitHub repository synthetic-sciences/openscience (3,432 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 721 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
architecture-diagram
Generate dark-themed SVG architecture diagrams as self-contained HTML.
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
analyze-terraform-plan
You are an expert Terraform plan analyser.
lambda-labs-gpu-cloud
Reserved and on-demand GPU cloud instances for ML training and inference. Use when you need dedicated GPU instances with simple SSH access, persistent filesystems, or high-performance multi-node clusters for large-scale training.
cloudflare-router
Use when manage Cloudflare DNS, CDN, and security rules via API. Use when configuring domains, SSL, WAF, or edge caching.
latchbio-integration
Build, register, debug, and operate bioinformatics workflows on Latch using the Python SDK, CLI, Latch Data and Registry, Nextflow, Snakemake, programmatic execution, and Latch MCP. Use when authoring or deploying Latch workflows, configuring resources or interfaces, moving data, integrating Registry, or launching and…