What is remove-custom?

A command that removes the active custom module repository and its installed files from claude-code-setup. These modules can include skills, MCP servers, command overrides, and scripts.

Use /remove-custom when you want to remove the currently installed custom repository and its tracked artifacts.

It removes custom additions and restores base command versions where custom commands replaced them.

remove-custom — Command by b33eep

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/b33eep/claude-code-setup/remove-custom

Clone the repo

git clone --depth 1 https://github.com/b33eep/claude-code-setup

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

When invoked 639 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00639
Opus 5	$0.00000	$0.00319
Sonnet 5	$0.00000	$0.00128
Haiku 4.5	$0.00000	$0.00064

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

Security

Grade C, and why

remove-custom scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

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

cd "$temp" && ./install.sh --remove-custom ; rm -rf "$temp"

commands/remove-custom.md · 87 lines

How it starts

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

Remove Custom Modules

Remove the active custom module repository and all its installed artifacts (skills, MCP servers, command overrides, scripts) from claude-code-setup.

Zero residue: deletes the git clone at ~/.claude/custom/, every installed copy, and every tracking entry; restores base versions for commands that overrode a base command.

Only one custom repo can be active at a time, so no URL argument is needed.

Usage

/remove-custom

Tasks

Check installation state
- If ~/.claude/installed.json doesn't exist → output the "no installation" message and stop.
- If installed.json has no custom_url AND ~/.claude/custom/ doesn't exist → output the "nothing to remove" message and stop.
Execute removal (1 Bash call)

Clone the latest claude-code-setup, run --remove-custom, then clean up:
```
temp=$(mktemp -d /tmp/claude-setup-XXXXXX) && \
git clone --depth 1 https://github.com/b33eep/claude-code-setup.git "$temp" 2>/dev/null && \
cd "$temp" && ./install.sh --remove-custom ; rm -rf "$temp"
```
The script handles:
- Removing every custom: skill from ~/.claude/skills/ and installed.json
- Removing every custom: MCP server from ~/.claude.json and installed.json
- Deleting every custom command override; restoring base versions when a base command exists in the claude-code-setup repo
- Deleting every custom script from ~/.claude/scripts/
- Deleting ~/.claude/custom/ (the git clone)
- Clearing custom_url and custom_version from installed.json
- Rebuilding ~/.claude/CLAUDE.md
Report
- Relay the counts printed by install.sh.
- If MCP servers were removed, remind the user to restart Claude Code.

Output

Success:

Removed custom repo: <url>

  - N skill(s)
  - M MCP server(s)
  - K command(s) (base versions restored where available)
  - L script(s)
  - ~/.claude/custom/
  - custom_url, custom_version

CLAUDE.md rebuilt.

IMPORTANT: Restart Claude Code to deactivate removed MCP servers.

Read the full file on GitHub · 87 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.

2d ago First seen · 87 lines · 0 tokens per session scan C a8b93f7a5ace

Subscribe to this mod's changes

remove-custom is a command published in the GitHub repository b33eep/claude-code-setup (56 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 639 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

ai ai-agents anthropic claude claude-code claude-code-plugin

remove-custom

Getting it into your agent

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

How it starts

Remove Custom Modules

Usage

Tasks

Output

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement