remoto-status

remoto-status is a command for Claude Code from JairoTorregrosa/jaiskills. It costs 18 tokens per session (128 once invoked), scanned A, original, MIT.

A command that shows the health of remote machines and the state of jobs running across them. A remote agent fleet is a group of computers running coding tasks outside the current machine.

In plain words
What is it for?
Use it to probe host health, list fleet jobs, inspect selected job results, and review logs for failures.
Why use it?
It gives you one view of running, finished, and failed jobs, including failure log tails. This avoids checking each remote host and job separately.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the jaiskills plugin — 12 skills, 13 commands, 4 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it to probe host health, list fleet jobs, inspect selected job results, and review logs for failures.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add JairoTorregrosa/jaiskills
Claude Code
/plugin install jaiskills

Made for: Claude Code.

Or install jaiskills, the plugin that ships this one along with the rest of its 12 skills, 13 commands, 4 agents, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for remoto-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/remoto-status/github.svg)](https://agentmods.dev/commands/jairotorregrosa/jaiskills/remoto-status)
Your own site
<a href="https://agentmods.dev/commands/jairotorregrosa/jaiskills/remoto-status"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/remoto-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for remoto-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/jairotorregrosa/jaiskills/remoto-status"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/remoto-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 128 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00128
Opus 5 $0.00009 $0.00064
Sonnet 5 $0.00004 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 11d ago against content hash 0eaf22e64894, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

remoto-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 11d 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.

commands/remoto-status.md · 12 lines

What it actually says

Using the remote-agents skill's CLI (${CLAUDE_PLUGIN_ROOT}/scripts/remoto.sh):

  1. Run hosts to probe host health.
  2. If job ids were given ($ARGUMENTS), run status on them and result for any that are DONE; otherwise run ls for the whole fleet.
  3. Summarize: what's running, what finished, what failed (include logs tail for failures).
Changes

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.

  1. 11d ago First seen · 12 lines · 18 tokens per session scan A 0eaf22e64894

Subscribe to this mod's changes

remoto-status is a command published in the GitHub repository JairoTorregrosa/jaiskills (5 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 128 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.