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 settings/corvidae-coding-projects/thermite/settingsgit clone --depth 1 https://github.com/Corvidae-Coding-Projects/ThermiteGrade 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 yesterday.
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 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.
- yesterday First seen · 101 lines scan A 1da8c54b4420
Thermite is a settings file published in the GitHub repository Corvidae-Coding-Projects/Thermite (52 stars, last pushed 24d 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
verified-polygon-intersection
Agent settings declaring 6 allowed tools.
chroma
Agent settings declaring 1 allowed tools.
skills
Agent settings declaring 1 hook event (PostToolUse).
anatomia
Agent settings declaring 1 hook event (SessionStart).
dravr-embacle
Agent settings declaring 1 hook event (SessionStart).
lean-interact
Agent settings declaring 56 allowed tools.