loop-status

A read-only status check for an existing mission loop, showing its saved state and latest validated event. A mission loop is a durable sequence of tracked work steps.

In plain words
What is it for?
It helps check the current status, iteration, last step, blocking reason, session, timestamp, and next safe action for a mission.
Why use it?
It lets you inspect progress without resuming the work, acquiring locks, or changing files. It reports specific problems when saved state is missing, outdated, or corrupted.

Command

Install

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.

agentmods
npx agentmods add commands/jcarlosrodicio/opencode-agent-orchestration-kit/loop-status
Clone the repo
git clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kit
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.00227
Opus 5 $0.00007 $0.00113
Sonnet 5 $0.00003 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured yesterday against content hash a112aabc6aee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

loop-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 yesterday.

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.

opencode/commands/loop-status.md · 25 lines

What it actually says

Estado de misión

Usa esta consulta para inspeccionar un loop existente sin reanudarlo ni modificarlo.

node scripts/mission-status.mjs --root /ruta/absoluta/al/repo --slug <slug>
node scripts/mission-status.mjs --root /ruta/absoluta/al/repo --slug <slug> --json

La salida proyecta el snapshot canónico y el último evento validado: status, iteration/planned, último paso, causa de bloqueo, sesión, timestamp y siguiente acción segura. --root debe ser una ruta absoluta y --slug un identificador kebab-case válido.

Si falta el estado, el snapshot está desfasado o el historial está corrupto, detente y reporta el código durable (state_missing, snapshot_stale o history_corrupt). No ejecutes resume, repair ni release como sustituto automático.

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. yesterday First seen · 25 lines · 14 tokens per session scan A a112aabc6aee

Subscribe to this mod's changes

loop-status is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 227 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-30.