remove
Skill2 starsChanged 45 days agoMITView on GitHub
Cleanly uninstall the model-guard statusline — unregisters statusLine from ~/.claude/settings.json (restoring any previously saved statusline), and optionally deletes the installed scripts and config.
- Deletes or force-pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Dariusplayer09/adaptive-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Dariusplayer09/adaptive-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read ~/.claude/model-guard.conf if present → note PREV_STATUSLINE_B64.
- Very specific: line 15
If the current statusLine is NOT model-guard (command doesn't contain model-guard), say so — only offer file cleanup (step 3b), don't touch …
- Very specific: line 29
If the conf has PREV_STATUSLINE_B64:
- Very specific: line 41
If ~/.config/kitty/kitty.conf carries the two remote-control lines that setup added (allow_remote_control socket-only, listen_on …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
model-guard: uninstall
You are removing the model-guard statusline for this user. Keep the final report short.
1. Inspect (one Bash call)
- Read
~/.claude/settings.json→.statusLine.command. - Read
~/.claude/model-guard.confif present → notePREV_STATUSLINE_B64. - If the current statusLine is NOT model-guard (command doesn't contain
model-guard), say so — only offer file cleanup (step 3b), don't touch settings.
2. Ask (ONE AskUserQuestion call)
Header "Cleanup": "Unregister + delete files (Recommended)" / "Unregister only (keep scripts & config)".
3. Execute
Backup first:
cp ~/.claude/settings.json ~/.claude/settings.json.bak-model-guard-$(date +%Y%m%d-%H%M%S)
a) Unregister — restore the pre-model-guard statusline if one was saved:
- If the conf has
PREV_STATUSLINE_B64:jq --argjson sl "$(sed -n 's/^PREV_STATUSLINE_B64=//p' ~/.claude/model-guard.conf | base64 -d)" \ '.statusLine=$sl' ~/.claude/settings.json > ~/.claude/settings.json.tmp \ && mv ~/.claude/settings.json.tmp ~/.claude/settings.json - Otherwise:
jq 'del(.statusLine)' ...(same tmp+mv pattern). - Validate the result parses:
jq . ~/.claude/settings.json >/dev/null.
b) If deleting files: rm -rf ~/.claude/model-guard; rm -f ~/.claude/model-guard.sh ~/.claude/model-guard.conf
(the flat model-guard.sh exists only on installs made before the directory layout)
and the per-session recovery state: rm -rf "${XDG_RUNTIME_DIR:-/tmp}/model-guard".
If ~/.config/kitty/kitty.conf carries the two remote-control lines that
setup added (allow_remote_control socket-only, listen_on unix:@kitty),
mention them — they are harmless, the user decides whether to keep them.
4. Report (short)
- StatusLine unregistered (and previous statusline restored, if there was one); a timestamped settings backup was kept.
- The plugin itself can be uninstalled with
/plugin→ Manage plugins, orclaude plugin uninstall model-guard@cli-model-guard.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

