Borrowing it
Nothing to install: this file belongs to Corvidae-Coding-Projects/Thermite. 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/Corvidae-Coding-Projects/Thermite/main/.claude/settings.jsongit clone --depth 1 https://github.com/Corvidae-Coding-Projects/ThermiteWrote 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/corvidae-coding-projects/thermite/settings)<a href="https://agentmods.dev/settings/corvidae-coding-projects/thermite/settings"><img src="https://agentmods.dev/badge/settings/corvidae-coding-projects/thermite/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/corvidae-coding-projects/thermite/settings"><img src="https://agentmods.dev/badge/settings/corvidae-coding-projects/thermite/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
Thermite 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 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"allowedTools": [
"Bash(tmux *)",
"Bash(git worktree *)"
],
"enableAllProjectMcpServers": true,
"hooks": {
"PostToolUse": [
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/.claude/hooks/post-edit-check.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; fi",
"timeout": 5,
"type": "command"
}
],
"matcher": "Write|Edit"
},
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/tooling/spec-discipline.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; fi",
"timeout": 5,
"type": "command"
}
],
"matcher": "Read"
},
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/.claude/hooks/heartbeat.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; fi",
"timeout": 3,
"type": "command"
}
]
}
],
"PreToolUse": [
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/.claude/hooks/pre-web-check.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; fi",
"timeout": 5,
"type": "command"
}
],
"matcher": "WebFetch|WebSearch"
},
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/.claude/hooks/work-check.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; fi",
"timeout": 3,
"type": "command"
}
],
"matcher": "Write|Edit|Bash"
},
{
"hooks": [
{
"command": "HOOK=\"$(git rev-parse --show-toplevel 2>/dev/null)/tooling/spec-discipline.py\"; if [ -f \"$HOOK\" ]; then python3 \"$HOOK\"; else exit 0; What else settings.json configures
This page is one entry in a file that holds 5. 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 · 101 lines scan A 1da8c54b4420
Thermite is a settings file published in the GitHub repository Corvidae-Coding-Projects/Thermite (54 stars, last pushed 2mo 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-30.
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.