A file-access guard that defines the exact files or folders Claude may read, edit, or write. Hooks block actions outside that boundary.

Use it to restrict Claude's work to selected files or directories during a coding task.

It reduces accidental changes to unrelated parts of a project when a task has a limited scope.

scope-lock — Plugin by gowtham012

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.

Claude Code

/plugin marketplace add gowtham012/Claude-plugins

agentmods

npx agentmods add plugins/gowtham012/claude-plugins/scope-lock

Clone the repo

git clone --depth 1 https://github.com/gowtham012/Claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

scope-lock scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

scope-lock/.claude-plugin/plugin.json · 19 lines

What it actually says

{
  "name": "scope-lock",
  "description": "Prevent scope creep. Define exact files/directories Claude can touch. PreToolUse hooks block Read/Write/Edit outside the boundary.",
  "version": "1.0.0",
  "author": {
    "name": "Gowtham"
  },
  "license": "MIT",
  "homepage": "https://github.com/gowtham012/Claude-plugins/tree/main/scope-lock",
  "repository": "https://github.com/gowtham012/Claude-plugins",
  "keywords": [
    "scope",
    "boundaries",
    "safety",
    "file-access",
    "guard",
    "focus"
  ]
}

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

marketplace.json 699 B

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.

yesterday First seen · 19 lines scan A a6e6078e81e3

Subscribe to this mod's changes

scope-lock is a plugin published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Languages Planning claude-code claude-plugin mcp open-source python session-persistence

scope-lock

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What ships with it

What this file has done since we first saw it

Other plugins, from other repositories

basic-memory

claude-code

wet-mcp

mainbranch

mainbranch

mnemo-mcp