ziniman/ai-install-guard

A Claude Code mod that runs in the background. Install it once, and every /plugin install, marketplace and MCP server, yours or Claude's, and every skill or settings change Claude makes, is checked before it lands: nothing to run, nothing to remember.
/plugin install ai-install-guard --marketplace ziniman/ai-install-guard
## What it does
Everything you add to Claude Code runs with your permissions: a plugin's hooks run every session, an MCP server can download and launch a package, a skill can carry hidden instructions. Checking it is usually a separate step you have to remember, and it never sees what Claude installs by itself.
AI Install Guard lives inside Claude Code instead. When something new is about to be added, it fetches the exact version, reads every file without running any of it, and holds it until you press Install or Reject.
Automatic. No command to run first: from the moment it is installed, it is in the way of every install.
It catches Claude too. What Claude adds on its own is checked like what you type, and waits for you unless it is something Claude wrote itself with no red flags.
Pinned. A verdict belongs to one commit and content hash, and only that version installs.
Local and open. No account or server, and every check is in this repository.
It holds /plugin install and /plugin marketplace add, and, when Claude does them: plugin installs, MCP servers it adds, skills, commands and agents it writes with a red flag, settings changes that widen what it may run, and the same changes made with a shell command. A mod that loads with files you never approved (picked from the /plugin menu, updated on its own, changed in place) is kept off until you approve it, a skill that came with no install (from a repository you cloned, copied in by hand) is checked as it is first used, and a plugin that is on but new or changed since the guard last looked (updated on its own, installed from a terminal) is checked as a session starts. A plugin picked from the menu is not scanned before it installs, so type /plugin install @ instead. Where it steps in has every case.
## Using it
Install plugins as you always do. The guard answers with a verdict in its pane:
No red flags: nothing suspicious. The "It can" line says what it would be able to do, so you can judge whether that fits.
Worth a look: something specific deserves a look first.
Do not install: a red flag. Installing it anyway asks twice.
Could not verify: the guard could not tell what would be installed. Installing it anyway asks twice.
Press Install (i) or Reject (r). When it holds a command Claude ran, approve it in the pane, then tell Claude to run it again.
To check something before you install it anywhere:
| Command | What it does |
| /guard scan | Scan it without installing it |
| /guard report | Reopen the last report |
| /guard list | Your approved and rejected versions |
| /guard held | The mods kept from loading, and the plugins on that wait for your decision |
| /guard forget | Forget a decision, so it is judged again |
The same scanner also runs in Claude chat, as a skill: Use it in Claude chat. For everything else, see How it works, Commands and the pane and the rest of the documentation.