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.
npx agentmods add skills/gowtham012/claude-plugins/locknpx skills add gowtham012/Claude-plugins --skill lockgit clone --depth 1 https://github.com/gowtham012/Claude-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00021 | $0.00324 |
| Opus 5 | $0.00010 | $0.00162 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
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 2d 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
Current scope state (auto-injected)
Config exists?
!`cat scope-lock/config.json 2>/dev/null || echo "(no config — run /scope-lock:setup first)"`
Instructions
The user wants to lock the scope to specific paths.
Arguments from user: $ARGUMENTS
Parse the arguments as a list of glob patterns. Common examples:
src/**— all files under src/tests/**— all files under tests/*.py— all Python files in the rootsrc/**/*.ts— all TypeScript files under src/
Ask the user for a reason if not provided. A short phrase is fine (e.g. "focusing on auth module refactor").
Call mcp__scope-lock__lock_scope with:
cwd= current working directorypaths= list of glob patterns parsed from argumentsreason= the reason for locking
Report the result. Remind the user:
Scope locked. All Read, Write, Edit, Bash, Glob, and Grep operations outside these paths will be blocked.
/scope-lock:status— check current scope/scope-lock:unlock— remove restrictions
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.
- 2d ago First seen · 43 lines · 21 tokens per session scan A 8d105a557581
lock is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 324 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
review-pr
Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to…
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
merge-pipecat-upstream
Merge the latest upstream pipecat-ai/pipecat tag into the pipecat submodule fork (dograh-hq/pipecat) and bump the dograh repo to it. Use whenever the user asks to bump, upgrade, sync, or merge pipecat, resolve pipecat merge conflicts, audit whether upstream changes break or supersede Dograh's in-fork patches, or…
cli-commands
MUST use when using the CLI, including debugging job failures and inspecting run history via wmill job.
write-script-bun
MUST use when writing TypeScript scripts. Bun is the default and preferred TypeScript runtime — pick it for TypeScript unless the script specifically needs Deno.
write-script-bunnative
MUST use when writing Bun Native scripts. The script must start with //native to run on the native worker.