runs

A command for listing workspace runs, which are recorded tasks started by coding-agent sessions, or checking one run’s status.

In plain words
What is it for?
Use it to list recent runs, include runs from other sessions, or inspect a named run.
Why use it?
It helps you see what tasks are running or finished without searching through separate sessions.

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/cpj-dev/dsh-plugin-cc/runs
Clone the repo
git clone --depth 1 https://github.com/cpj-dev/dsh-plugin-cc
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 120 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.00120
Opus 5 $0.00007 $0.00060
Sonnet 5 $0.00003 $0.00024
Haiku 4.5 $0.00001 $0.00012

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

Security

Grade A, and why

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

plugins/dsh/commands/runs.md · 13 lines

What it actually says

List runs (newest first), or show one run's status when the user names an id:

node "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" runs "$ARGUMENTS"

--all includes runs from other Claude sessions in this workspace. Present the listing verbatim; suggest /dsh:show <run-id> for finished runs and /dsh:stop <run-id> for stuck ones.

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 · 13 lines · 14 tokens per session scan A 136ec697af23

Subscribe to this mod's changes

runs is a command published in the GitHub repository cpj-dev/dsh-plugin-cc (106 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 120 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.