Where RepoGates checks

Each part of RepoGates, where it works and what it does not see: the browser extension, the Claude Code plugin, the MCP server, the Claude skill, the deep scan, the agent check-up and the terminal command.

Each part, and what it does not see

RepoGates is several parts that ask the same verdict service. Each one works in one place, and each one's limit is stated here with it. Nothing below runs a repository's code, and none of it is an audit.

PartWhere it worksWhat it does not see
Browser extension (Chrome, Edge) The board on github.com, gitlab.com and huggingface.co pages, and the gate that holds a download from those hosts while the verdict is fetched (the gate). The browser extension does not see git clone, package managers or curl: it lives in the browser, and a browser extension cannot see another process.
Claude Code plugin A hook on Claude Code's Bash tool sends the command line to the preflight before it runs (the plugin). It does not see git clone, package managers or curl — outside Claude Code with the RepoGates plugin, whose hook refuses a clone or install that names a blocked repository on the command line, before it runs. The hook sees Bash tool calls in that one client and nothing else. Edit and Write are read for one thing only — an API key about to be saved — checked on the machine and never sent; that guard asks, it never denies.
MCP server Twelve tools an AI agent can call before it fetches: preflight, check_repo, check_download_url, check_skill and others (the tools). It answers what an agent asks it. An agent that never calls it is not stopped.
Claude skill (claude.ai, Cowork) Tells Claude to ask the MCP server before it fetches code (the skill). It is an instruction, not a control: it works when the agent follows it.
Deep scan Reads a repository, package, image or skill in a sandbox with the scan engines, on credits (deep scans). It reads files; it never runs them. A large source may be read in part, and a partial scan says so and is never a PASS.
Agent check-up Inventories the plugins, skills, MCP servers, hooks and permission rules already on your machine (the check-up). It sends RepoGates identifiers, never contents. It reads configuration; it does not see what a plugin or server does when it runs.
At a terminal repogates check and repogates clone ask the preflight before a clone or install you type (at a terminal). It sees only what is run through it.

The open gap

A git clone, a package manager or a curl typed in a plain terminal, not through repogates check or repogates clone, reaches no part of RepoGates. Neither does an agent other than Claude Code that never calls the MCP server. These are stated, not hidden; what is planned is on the roadmap.

← All documentation · What a verdict means · AI agents