remove

A removal command for the Claude Code status line setup, which displays information in the coding assistant’s interface.

In plain words
What is it for?
Use it to delete all status line files and settings, remove only the configuration, or cancel the removal.
Why use it?
It helps remove the status line and its related files after asking which parts to delete.

Command

Part of the claude-telemetry plugin — 3 commands, 1 hook shipped together

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/jeongph/claude-telemetry/remove
Clone the repo
git clone --depth 1 https://github.com/jeongph/claude-telemetry

Or install claude-telemetry, the plugin that ships this one along with the rest of its 3 commands, 1 hook.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 905 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.00006 $0.00905
Opus 5 $0.00003 $0.00452
Sonnet 5 $0.00001 $0.00181
Haiku 4.5 $0.00001 $0.00090

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

Security

Grade D, and why

remove scanned grade D with 2 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 3d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. Read `~/.claude/settings.json`

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/.claude/statusline/
commands/remove.md · 130 lines

How it starts

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

Status Line Removal

You are removing the claude-telemetry status line configuration.

Execution Flow

Execute steps 1 → 2 → 3 → 4 sequentially. Do NOT skip steps.


Step 1: Detect Language

  1. Read ~/.claude/settings.json
  2. Check the language field
  3. Map: "한국어" → ko, "English" → en, "日本語" → ja, "中文" → zh. Default: en
  4. Use this language for ALL user-facing text

Step 2: Confirm Removal

Call AskUserQuestion with EXACTLY this structure (translate to detected language):

{
  "questions": [{
    "question": "<translated: Remove the status line configuration? This will delete config, binary, cache, and disable the status line.>",
    "header": "Remove",
    "multiSelect": false,
    "options": [
      {
        "label": "<translated: Remove all>",
        "description": "<translated: Delete config, binary, cache directory, and remove statusLine from settings.json>"
      },
      {
        "label": "<translated: Config only>",
        "description": "<translated: Delete config file only, keep binary and statusLine entry>"
      },
      {
        "label": "<translated: Cancel>",
        "description": "<translated: Do nothing>"
      }
    ]
  }]
}

If user selects "Cancel", output a cancellation message and stop.


Step 3: Remove Configuration

Based on user choice:

"Remove all"

  1. Run the tested cleanup path in the binary (removes statusLine from settings.json with backup, deletes config/binary/marker, neutralizes run.sh):
    ~/.claude/statusline/bin/claude-telemetry --self-uninstall && echo "CLEANED" || echo "FALLBACK"
    
  2. If CLEANED → proceed to Step 4. A backup was saved at ~/.claude/settings.json.claude-telemetry.bak.
  3. If FALLBACK (binary missing or failed) → do it manually:
    1. Remove files:
      rm -rf ~/.claude/statusline/
      
    2. Read ~/.claude/settings.json
    3. Remove the "statusLine" entry from the JSON using Edit tool
    4. Verify settings.json is still valid JSON:
      python3 -c "import json; json.load(open('$HOME/.claude/settings.json'))" 2>/dev/null || echo "INVALID"
      
      If invalid, warn the user and suggest manual fix.

Read the full file on GitHub · 130 lines

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. 3d ago First seen · 130 lines · 6 tokens per session scan D 763d83bd5b50

Subscribe to this mod's changes

remove is a command published in the GitHub repository jeongph/claude-telemetry (5 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 905 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.