uninstall

uninstall is a skill for Claude Code from ai-native-sys/claude-code-tools. It costs 16 tokens per session (450 once invoked), scanned D, original, MIT.

Instructions for removing the claude-code-tools HUD statusline, a display that shows status information in the command-line interface. It covers configuration, caches, logs, and preserving settings.

In plain words
What is it for?
Use it when uninstalling the HUD, deciding whether to keep its configuration, and cleaning up its cache and log files.
Why use it?
It helps remove the add-on's files and configuration without disturbing a different statusline plugin or unrelated settings.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the hud plugin — 2 skills shipped together

Good fit Use it when uninstalling the HUD, deciding whether to keep its configuration, and cleaning up its cache and log files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ai-native-sys/claude-code-tools/uninstall
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.

Any agent
npx skills add ai-native-sys/claude-code-tools --skill uninstall
Clone the repo
git clone --depth 1 https://github.com/ai-native-sys/claude-code-tools

Made for: Claude Code.

Or install hud, the plugin that ships this one along with the rest of its 2 skills.

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 uninstall

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/uninstall/github.svg)](https://agentmods.dev/skills/ai-native-sys/claude-code-tools/uninstall)
Your own site
<a href="https://agentmods.dev/skills/ai-native-sys/claude-code-tools/uninstall"><img src="https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/uninstall/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 uninstall

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-native-sys/claude-code-tools/uninstall"><img src="https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/uninstall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 450 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.00016 $0.00450
Opus 5.5 $0.00006 $0.00180
Sonnet 5.5 $0.00003 $0.00090
Haiku 4.5 $0.00002 $0.00045

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

Security

Grade D, and why

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

Reads agent configuration directoriesmediumAgent snooping

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

1. Remove the `statusLine` entry from `~/.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/plugins/claude-code-tools/hud/cache
plugins/hud/skills/uninstall/SKILL.md · 55 lines

What it actually says

Uninstall claude-code-tools HUD

Guide the user through cleanly removing the HUD statusline plugin.

Step 1: Confirm with user

Tell the user this will:

  1. Remove the statusLine entry from ~/.claude/settings.json
  2. Delete HUD config, cache, and log files from ~/.claude/plugins/claude-code-tools/hud/

Ask the user to confirm before proceeding. Also ask if they want to keep their config file in case they reinstall later.

Step 2: Remove statusLine from settings

  1. Read ~/.claude/settings.json
  2. Check if the statusLine field exists and contains a reference to hud (look for claude-code-tools/hud in the command string)
  3. If it matches, remove the statusLine field entirely. Do NOT remove it if it points to a different statusline plugin (e.g., claude-hud).
  4. Preserve all other settings and write back.

If the statusLine doesn't reference our hud plugin, inform the user and skip this step.

Step 3: Clean up data files

Remove the HUD data directory:

rm -rf ~/.claude/plugins/claude-code-tools/hud/cache
rm -rf ~/.claude/plugins/claude-code-tools/hud/logs

If the user chose to keep their config, skip deleting the config file. Otherwise:

rm -f ~/.claude/plugins/claude-code-tools/hud/config.json

If the directory is now empty, remove it:

rmdir ~/.claude/plugins/claude-code-tools/hud 2>/dev/null

Step 4: Report result

Tell the user the HUD statusline has been removed. The statusline will disappear on the next Claude Code render cycle (no restart needed).

If they want to reinstall later, they can run /hud:setup again.

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 · 55 lines · 16 tokens per session scan D 4788e7319ce7

Subscribe to this mod's changes

uninstall is a skill published in the GitHub repository ai-native-sys/claude-code-tools (1 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens