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 hooks/shanraisshan/claude-code-hooks/file-changedgit clone --depth 1 https://github.com/shanraisshan/claude-code-hooksWrote 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/shanraisshan/claude-code-hooks/file-changed)<a href="https://agentmods.dev/hooks/shanraisshan/claude-code-hooks/file-changed"><img src="https://agentmods.dev/badge/hooks/shanraisshan/claude-code-hooks/file-changed.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
FileChanged 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 4d 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.
This is a copy
100% identical to FileChanged — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"FileChanged": [
{
"matcher": ".envrc|.env|.env.local",
"hooks": [
{
"type": "command",
"command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
"timeout": 5000,
"async": true,
"statusMessage": "FileChanged"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 31. Installing the file brings all of them; each is measured and scanned on its own page.
- Settings file claude-code-hooks A not measured
- Hook ConfigChange A not measured
- Hook CwdChanged A not measured
- Hook Elicitation A not measured
- Hook ElicitationResult A not measured
- Hook InstructionsLoaded A not measured
- Hook MessageDisplay A not measured
- Hook Notification A not measured
- Hook PermissionDenied A not measured
- Hook PermissionRequest A not measured
- Hook PostCompact A not measured
- Hook PostToolBatch A not measured
- Hook PostToolUse A not measured
- Hook PostToolUseFailure A not measured
- Hook PreCompact A not measured
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook SessionStart A not measured
- Hook Setup A not measured
- Hook Stop A not measured
- Hook StopFailure A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop A not measured
- Hook TaskCompleted A not measured
- Hook TaskCreated A not measured
- Hook TeammateIdle A not measured
- Hook UserPromptExpansion A not measured
- Hook UserPromptSubmit A not measured
- Hook WorktreeCreate A not measured
- Hook WorktreeRemove A not measured
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 First seen · 16 lines scan A a1436e6e0aac
FileChanged is a hook published in the GitHub repository shanraisshan/claude-code-hooks (531 stars, last pushed 3mo ago), licensed MIT. 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. It is 100% identical to FileChanged, differing in 0 lines, and is treated as a copy.
Other hooks, from other repositories
FileChanged
Runs on the FileChanged event for .envrc, .env and .env.local tool calls, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.
PreToolUse
Runs before the agent uses a tool, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.
Setup
Runs once when the project is set up, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.
PostToolUse
Runs after a tool call finishes, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.
PostCompact
Runs after the context is compacted, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.
TaskCompleted
Runs when a task is marked completed, executing hooks.py via python3. From shanraisshan/claude-code-best-practice.