Borrowing it
Nothing to install: this file belongs to lkangd/cc-settings-preset. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lkangd/cc-settings-preset/main/.claude/settings.jsongit clone --depth 1 https://github.com/lkangd/cc-settings-presetWrote 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/hooks/lkangd/cc-settings-preset/stop)<a href="https://agentmods.dev/hooks/lkangd/cc-settings-preset/stop"><img src="https://agentmods.dev/badge/hooks/lkangd/cc-settings-preset/stop/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/hooks/lkangd/cc-settings-preset/stop"><img src="https://agentmods.dev/badge/hooks/lkangd/cc-settings-preset/stop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
Stop 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 2mo ago.
A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.
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
{
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "bash -c 'set -o pipefail; run() { local out code; out=$(\"$@\" 2>&1); code=$?; if [ $code -ne 0 ]; then echo \"Stop hook: $* failed (exit $code)\" >&2; echo \"$out\" >&2; exit 2; fi; }; run pnpm run typecheck; run pnpm run build; run pnpm run test -- --reporter=dot --silent=passed-only'",
"timeout": 120,
"statusMessage": "Running build & test..."
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 2mo ago First seen · 14 lines scan A 0a469b80861e
Stop is a hook published in the GitHub repository lkangd/cc-settings-preset (5 stars, last pushed 1mo ago), licensed ISC. Its token cost is not measured: a hook is shell that never enters the context. 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 hooks, from other repositories
7
Runs on the 7 event for Write tool calls, executing post-edit-check.js via node. From rohitg00/awesome-claude-code-toolkit.
9
Runs on the 9 event for Write tool calls, executing lint-fix.js via node. From rohitg00/awesome-claude-code-toolkit.
14
Runs on the 14 event for Edit tool calls, executing auto-test.js via node. From rohitg00/awesome-claude-code-toolkit.
15
Runs on the 15 event for Write tool calls, executing bundle-check.js via node. From rohitg00/awesome-claude-code-toolkit.
18
Runs on the 18 event, executing context-loader.js via node. From rohitg00/awesome-claude-code-toolkit.
24
Runs on the 24 event, executing prompt-check.js via node. From rohitg00/awesome-claude-code-toolkit.