app-run-status

A run-status command that checks an append-only record of agent executions and detects abandoned or invalid attempts. A lease is a time-limited record showing that an attempt is still active.

In plain words
What is it for?
Use it to inspect durable execution state before dispatching work and to identify attempts that need recovery or interruption.
Why use it?
It prevents new work from being dispatched when execution records are missing, malformed, expired, or show conflicting active attempts.

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/vmobifystudio/app-dev-team/app-run-status
Clone the repo
git clone --depth 1 https://github.com/vmobifystudio/app-dev-team
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 113 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.00000 $0.00113
Opus 5 $0.00000 $0.00056
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00011

Measured 2d ago against content hash 22516a76d563, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

app-run-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 2d 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/app-run-status.md · 12 lines

What it actually says

/app-run-status — inspect durable execution state

Use the append-only run ledger and fail-closed orphan detector:

node "${CLAUDE_PLUGIN_ROOT}/scripts/run-doctor.mjs" --ledger "$RUN_LEDGER"

CLEAR means active attempts have valid, unexpired leases and there is at most one active attempt per run. ANOMALIES means stop dispatching and recover or interrupt the named attempt. Missing or malformed ledgers are CANNOT EVALUATE, not a green result.

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. 2d ago First seen · 12 lines · 0 tokens per session scan A 22516a76d563

Subscribe to this mod's changes

app-run-status is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 113 tokens. 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.