Borrowing it
Nothing to install: this file belongs to PowerBeef/Vocello. 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/PowerBeef/Vocello/main/.claude/settings.jsongit clone --depth 1 https://github.com/PowerBeef/VocelloWrote 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/settings/powerbeef/vocello/settings)<a href="https://agentmods.dev/settings/powerbeef/vocello/settings"><img src="https://agentmods.dev/badge/settings/powerbeef/vocello/settings/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/settings/powerbeef/vocello/settings"><img src="https://agentmods.dev/badge/settings/powerbeef/vocello/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade D, and why
Vocello scanned grade D with 2 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
"Bash(sudo *)", Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"Bash(rm -rf build)", How it starts
The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"worktree": {
"baseRef": "head"
},
"hooks": {
"SessionStart": [
{
"matcher": "startup|resume|clear|compact|fork",
"hooks": [
{
"type": "command",
"command": "python3 \"$CLAUDE_PROJECT_DIR/scripts/hooks/worker_lifecycle.py\"",
"timeout": 10
},
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR/scripts/hooks/session_start.sh\"",
"timeout": 15
}
]
}
],
"PreToolUse": [
{
"matcher": "^Bash$",
"hooks": [
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR/scripts/hooks/commit_lint.sh\"",
"timeout": 15
},
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR/scripts/hooks/policy_guard.sh\"",
"timeout": 10
},
{
"type": "command",
"command": "python3 \"$CLAUDE_PROJECT_DIR/scripts/hooks/agent_guard.py\"",
"timeout": 10
}
]
},
{
"matcher": "^(Edit|Write|MultiEdit|NotebookEdit)$",
"hooks": [
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR/scripts/hooks/generated_file_guard.sh\"",
"timeout": 10
},
{
"type": "command",
"command": "python3 \"$CLAUDE_PROJECT_DIR/scripts/hooks/agent_guard.py\"",
"timeout": 10
}
]
},
{
"matcher": "^mcp__",
"hooks": [
{
"type": "command",
"command": "python3 \"$CLAUDE_PROJECT_DIR/scripts/hooks/simulator_tool_guard.py\"",
"timeout": 5
}
]
}
],
"PostToolUse": [
{
"matcher": "^(Edit|Write|MultiEdit|NotebookEdit)$",
"What else settings.json configures
This page is one entry in a file that holds 7. 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.
- 4d ago Changed · +6 lines a6a444e914a3
- 10d ago Changed · +10 lines 8ff8f179e76e
- 15d ago Changed · +48 lines 57ce5d777abd
- 16d ago Changed · +102 lines scan C → D be79d6df510d
- 22d ago Changed · +2 lines ad7ca1c297d2
- 28d ago Changed · +1 lines ab4e0155ca10
- 29d ago Changed · +1 lines eec3df6176cd
- 1mo ago Changed · +1 lines 21dce23384e7
- 1mo ago Changed 43514d060e78
- 1mo ago First seen · 183 lines scan C 3241d5f8602a
Vocello is a settings file published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), 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 D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.