The skill that makes Claude check a repository, model, extension or skill before it clones or installs, in Claude.ai and Cowork.
Claude.ai and Cowork have no hook, so nothing there is enforced. What
they can have is the same behaviour the plugin carries, as a skill:
repogates-vetting tells Claude to check RepoGates before
any clone, download or install, to stop on a refusal and never route
around it, to tell you what fired on a warning, and to say so plainly
when the connector is missing. It is one file, packaged as a zip and
served from this site — not fetched from GitHub:
Download repogates-vetting-skill.zip
https://mcp.repogates.com/mcp.
It signs you in with OAuth the first time a tool runs; a paid
RepoGates plan is required.repogates_status to prove the connector is there, then
preflight on the exact line — git clone …,
npm install express, pip install flask —
and acts on the answer: on allow it proceeds under
Claude's own rules; on ask it tells you what fired and
waits; on a refusal it stops, quotes the reason, and does not fetch
the repository another way. On a REVIEW it may offer a
deep_scan of the files — priced in credits by size, only after
your yes to that call.What this is not: enforcement. An agent that ignores the skill is
not stopped, exactly as curl is not stopped — the skill
says so itself, and the response to every call says
enforced: false. Inside Claude Code the same lines meet
the plugin's hook, which refuses a denied line before the Bash tool
runs it — there is no prompt to argue with.