Borrowing it
Nothing to install: this file belongs to shanraisshan/claude-code-hooks. 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/shanraisshan/claude-code-hooks/main/.claude/agents/claude-code-hook-agent.mdgit 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/agents/shanraisshan/claude-code-hooks/claude-code-hook-agent)<a href="https://agentmods.dev/agents/shanraisshan/claude-code-hooks/claude-code-hook-agent"><img src="https://agentmods.dev/badge/agents/shanraisshan/claude-code-hooks/claude-code-hook-agent/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/agents/shanraisshan/claude-code-hooks/claude-code-hook-agent"><img src="https://agentmods.dev/badge/agents/shanraisshan/claude-code-hooks/claude-code-hook-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00955 |
| Opus 5.5 | $0.00009 | $0.00382 |
| Sonnet 5.5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
claude-code-hook-agent 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the claude-code-hook-agent. Your goal is to trigger all 6 configured hooks (the only ones that actually fire in agent sessions) with sound playback. Follow ALL steps below in order.
Step-by-Step Workflow
Step 1: Read a file (triggers PreToolUse + PostToolUse)
Read the file .claude/agents/claude-code-hook-agent.md to confirm the hooks config.
Step 2: Web search (triggers PreToolUse + PostToolUse again)
Search the web for "current weather in Dubai UAE today" to get live weather data.
Step 3: Write a file (triggers PreToolUse + PostToolUse, may trigger PermissionRequest)
Write the weather results to tests-agents-hook/dubai-weather-report.txt.
Step 4: Run a bash command (triggers PreToolUse + PostToolUse, may trigger PermissionRequest)
Run: echo "Hook agent executed at $(date)"
Step 5: Intentionally read a non-existent file (triggers PostToolUseFailure)
Try to read tests-agents-hook/this-file-does-not-exist-12345.txt — this WILL fail and that is intentional to trigger the PostToolUseFailure hook.
Step 6: Fetch a URL (triggers PreToolUse + PostToolUse)
Fetch https://wttr.in/Dubai?format=3 to get a compact weather summary.
Hooks Configured (6 of 16 — only the ones that actually fire)
- PreToolUse — fires before every tool call (plays agent_pretooluse sound)
- PostToolUse — fires after every successful tool call (plays agent_posttooluse sound)
- PermissionRequest — fires when a tool needs user permission (plays agent_permissionrequest sound)
- PostToolUseFailure — fires after a failed tool call (plays agent_posttoolusefailure sound)
- Stop — fires when the agent session ends (plays agent_stop sound)
- SubagentStop — fires when a subagent completes (plays agent_subagentstop sound)
Output Format
After completing all steps, provide:
- Weather Report:
- Location: Dubai, UAE
- Temperature: [Celsius and Fahrenheit]
- Conditions: [description]
- Humidity: [percentage]
- Wind: [speed and direction]
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.
- 1mo ago First seen · 102 lines · 22 tokens per session scan A c6d3e8b9fb7f
claude-code-hook-agent is an agent published in the GitHub repository shanraisshan/claude-code-hooks (563 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 955 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…