A command for checking an RLM execution chain, which is a task split into smaller pieces and processed in stages. It shows the chain's status, progress, subtasks, and results.

Use it to monitor an RLM chain by its ID and optionally inspect full details for every subtask.

It lets you see whether a long analysis is still running, what has finished, and whether any part has failed. A detailed view helps identify the exact state of each subtask.

rlm-status — Command for Claude Code by joseairosa

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.

Clone the repo

git clone --depth 1 https://github.com/joseairosa/recall

Made for: Claude Code.

Or install claude-plugin, the plugin that ships this one along with the rest of its 7 commands, 3 agents, 5 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/joseairosa/recall/rlm-status/github.svg)](https://agentmods.dev/commands/joseairosa/recall/rlm-status)

Your own site

<a href="https://agentmods.dev/commands/joseairosa/recall/rlm-status"><img src="https://agentmods.dev/badge/commands/joseairosa/recall/rlm-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/joseairosa/recall/rlm-status"><img src="https://agentmods.dev/badge/commands/joseairosa/recall/rlm-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 748 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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00748
Opus 5	$0.00008	$0.00374
Sonnet 5	$0.00003	$0.00150
Haiku 4.5	$0.00002	$0.00075

Measured 9d ago against content hash 65729474661a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

rlm-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 9d 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.

claude-plugin/commands/rlm-status.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.