exp-status

exp-status is a command for Claude Code from zhyx12/projtool. It costs 14 tokens per session (469 once invoked), scanned A, original, MIT.

A project command that displays the status of active runs, experiment instances, file-sync sessions, and recent runs. An experiment run is one execution of a configured experiment.

In plain words
What is it for?
Checking instance and sync health, reviewing active or recently finished runs, and diagnosing problems when the status checks report something unusual.
Why use it?
It gathers several project-health checks into one compact dashboard so you can quickly see what is running or needs attention.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Checking instance and sync health, reviewing active or recently finished runs, and diagnosing problems when the status checks report something unusual.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zhyx12/projtool/exp-status
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/zhyx12/projtool

Made for: Claude Code.

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 exp-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/zhyx12/projtool/exp-status/github.svg)](https://agentmods.dev/commands/zhyx12/projtool/exp-status)
Your own site
<a href="https://agentmods.dev/commands/zhyx12/projtool/exp-status"><img src="https://agentmods.dev/badge/commands/zhyx12/projtool/exp-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 exp-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/zhyx12/projtool/exp-status"><img src="https://agentmods.dev/badge/commands/zhyx12/projtool/exp-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 469 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.00014 $0.00469
Opus 5.5 $0.00006 $0.00188
Sonnet 5.5 $0.00003 $0.00094
Haiku 4.5 $0.00001 $0.00047

Measured 2mo ago against content hash 8f900ec17649, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

exp-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 2mo 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.

src/projtool/assets/project_templates/claude/commands/exp-status.md · 49 lines

What it actually says

You are running the user's /exp-status command. Produce a compact dashboard, not a wall of text.

Steps

  1. Call mcp__projtool__list_syncs — get mutagen session health.
  2. Call mcp__projtool__list_runs filtered to runs whose manifest status is running or finished within the last 24h.
  3. Call mcp__projtool__worktree_status for the active worktree.
  4. (Cheap, optional) call mcp__projtool__diagnose only if any of the above surfaces something off — don't run a full diagnose if everything is green.

Output format

Print one short table for instances/syncs and one for recent runs. Use the following structure (markdown):

### Instances
| experiment   | state    | uuid   | ssh alias       |
|--------------|----------|--------|-----------------|
| exp-layernorm| bound    | i-abc..| autodl-layernorm|

### Syncs
| name             | status      | last_event |
|------------------|-------------|------------|
| outputs          | watching    | 2m ago     |
| layernorm-code   | watching    | 30s ago    |

### Runs (active or recent)
| run_id                          | status    | metric_summary    |
|---------------------------------|-----------|-------------------|
| exp-layernorm/2026-05-08T22:14Z | running   | epoch 12/40       |
| exp-baseline/2026-05-08T18:01Z  | completed | best_val_acc=0.873|

If something is unhealthy (sync paused, manifest stale, instance disappeared from AutoDL but binding says bound), call it out beneath the table with a recommended fix (often sync_resume or refresh_ssh).

What NOT to do

  • Don't list manifests in full — a one-line summary per run is enough.
  • Don't fetch every run from history. Cap at the most recent ~10.
  • Don't hand-roll ssh / git / mutagen commands; use the MCP tools.
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. 2mo ago First seen · 49 lines · 14 tokens per session scan A 8f900ec17649

Subscribe to this mod's changes

exp-status is a command published in the GitHub repository zhyx12/projtool (1 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 469 once invoked, about $0.0001 per session on Opus 5.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.

Related

exp-status compared with commands from other repositories

exp-status next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
exp-statuszhyx12/projtoolCommand12mo agoMITA14Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code