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 commands/vast-ai/vast-claude-plugin/statusgit clone --depth 1 https://github.com/vast-ai/vast-claude-pluginWrote 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/commands/vast-ai/vast-claude-plugin/status)<a href="https://agentmods.dev/commands/vast-ai/vast-claude-plugin/status"><img src="https://agentmods.dev/badge/commands/vast-ai/vast-claude-plugin/status.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.1 | $0.00012 | $0.00562 |
| Opus 5 | $0.00006 | $0.00281 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
status 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 6d ago.
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.
What it actually says
/vast:status
Show the current state of one or all Vast.ai instances. Does not poll — this is a single snapshot. For poll-until-running behavior, ask in natural language; the vastai skill handles polling with a timeout.
Steps
-
If
$ARGUMENTSis empty: list all instances.vastai show instances-v1 --raw -a-a/--allauto-fetches every page, sidestepping the interactiveFetch next page? (y/N)prompt that otherwise fires under--raw. If you only need one page, pass--limit <N>instead — read the current per-page cap fromvastai show instances-v1 --help.The response is an object
{instances: [...], instances_found: N}. Groupinstances[]byactual_status(running / loading / exited / stopped / unknown / offline). Show id, label, gpu_name, num_gpus, and$/hrfor each. -
If
$ARGUMENTSis a numeric instance id: show just that instance.vastai show instance "$ARGUMENTS" --rawReport
actual_status,intended_status,gpu_name,cur_state,next_state, and the$/hrrate. Ifactual_statusisexited,unknown, oroffline, flag this as a terminal state — the user shouldvastai destroy instance <id> -yto stop disk charges accruing. -
Triage 401 responses. Both
show instances-v1andshow instanceare 2FA-gated.- Body contains
"Two Factor Authentication"→ recommend!vastai tfa login --method-type totp --code <CODE>(!prefix keeps the code out of the transcript), then retry. - Other 401 → see
/vastai:setupstep 4 triage.
- Body contains
Notes
--rawis required to parse the JSON response.- The status enum and what each state means live in
skills/vastai/SKILL.md§ "Instance status values". - Never loop on this command without a timeout — terminal states (
exited/unknown/offline) signal the instance won't recover. - For SSH connection failures on a
runninginstance, pullvastai logs <id>FIRST before any other recovery (skill Critical rule 11).
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.
- 6d ago First seen · 37 lines · 12 tokens per session scan A 2e3efe382c6e
status is a command published in the GitHub repository vast-ai/vast-claude-plugin (3 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 562 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
account
This API allows you to manage your Scaleway Projects.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.