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.
git clone --depth 1 https://github.com/gowtham012/Claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/gowtham012/claude-plugins/scope-lock)<a href="https://agentmods.dev/plugins/gowtham012/claude-plugins/scope-lock"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/scope-lock/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/gowtham012/claude-plugins/scope-lock"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/scope-lock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo ago.
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.
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"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 34 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
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.
- 1mo ago First seen · 19 lines scan A a6e6078e81e3
scope-lock is a plugin published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 7mo 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.
Other plugins, from other repositories
alibabacloud-opc
Alibaba Cloud OPC (one-person company) package selection and provisioning for solo developers, with an itemized monthly cost confirmation before any charge.
threat-model
Produce threat models for open-source projects: the security contract between a project and its users, structured for downstream integrators and vulnerability triagers.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
looptimal
Turns an objective into a delivered, VERIFIED OUTCOME: frames a hash-pinned sealed acceptance suite, designs the right loop (the loop-design wizard, formerly LoopPrint), war-games it forward, executes with dynamic domain-expert sub-agents (maker != checker), and gates completion on a separate verifier re-running the…
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.
huntress
Every Huntress endpoint, plus fleet-wide incident, coverage, and billing rollups the API can't.