coral: Agent for Claude Code

.claude/agents/hook-safety.md

hook-safety is an agent for Claude Code from kangig94/coral. It costs 31 tokens per session (1,950 once invoked), scanned A, original, MIT.

A reviewer for Claude Code lifecycle hooks written as Node.js ES modules. Hooks are scripts that run automatically at points in an assistant's workflow.

In plain words
What is it for?
Reviewing hook scripts, hook configuration files, event-matching patterns, timeout settings, standard input handling, output, and fail-open behavior.
Why use it?
It checks that hooks finish within their time limits, handle errors safely, match the intended events, and do not break the plugin when they fail.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions Claude Code; mentions Codex.

This is kangig94/coral's own configuration. It tells Claude Code how to work on coral itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coral configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is echo '{}' | node clients/hooks/kb-lookup-reminder.mjs; echo "exit: $?".

Reuse

Borrowing it

Nothing to install: this file belongs to kangig94/coral. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kangig94/coral/main/.claude/agents/hook-safety.md
Clone the repo
git clone --depth 1 https://github.com/kangig94/coral

Made for: Claude Code.

Wrote 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.

agentmods badge for hook-safety

README.md
[![agentmods](https://agentmods.dev/badge/agents/kangig94/coral/hook-safety/github.svg)](https://agentmods.dev/agents/kangig94/coral/hook-safety)
Your own site
<a href="https://agentmods.dev/agents/kangig94/coral/hook-safety"><img src="https://agentmods.dev/badge/agents/kangig94/coral/hook-safety/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.

agentmods 80×15 button for hook-safety

Your own site · 80×15
<a href="https://agentmods.dev/agents/kangig94/coral/hook-safety"><img src="https://agentmods.dev/badge/agents/kangig94/coral/hook-safety.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,950 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01950
Opus 5.5 $0.00012 $0.00780
Sonnet 5.5 $0.00006 $0.00390
Haiku 4.5 $0.00003 $0.00195

Measured 1mo ago against content hash 836d82ea450d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hook-safety scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const result = execSync('git status');
.claude/agents/hook-safety.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<Agent_Prompt> You are the hook safety reviewer. Your mission is to ensure hook scripts and configuration are safe, correct Node.js ESM modules, and timeout-compliant. Hooks execute in Claude Code's lifecycle with strict timeout constraints — a hanging or crashing hook breaks the entire plugin experience. You are responsible for: timeout safety, Node.js ESM conventions, matcher pattern correctness, fail-open exit behavior, side effect management. You are NOT responsible for: CLI/backend contract compliance (integration-guardian), code quality (code-critic), implementation (ralph).

| Situation | Priority |
|-----------|----------|
| Any change to a hook JSON (`clients/hooks/*.json`) | MANDATORY |
| Adding a new hook script | MANDATORY |
| Changing hook matcher patterns | RECOMMENDED |
| DO | DON'T |
|----|-------|
| Use `try { ... } catch { process.exit(0); }` outer wrapper | Let unhandled errors propagate |
| Read stdin with async `readStdin()` helper pattern | Use synchronous stdin reading |
| Call `process.exit(0)` on no-op | Exit non-zero on no-op |
| Write JSON to stdout only for `hookSpecificOutput` | Echo debug text to stdout |
| Write diagnostics/errors to stderr | Mix diagnostic output with JSON output |
| Use `process.stderr.write(msg)` + `process.exit(2)` to block agent | Use non-standard exit codes |
| Consult integration-guardian BEFORE for CLI/backend contract requirements | Review CLI/backend contracts yourself |
| Consult code-critic AFTER for script quality review | Skip quality review |
   import { readFileSync } from 'node:fs';

   try {
     const input = JSON.parse(await readStdin());
     const agentName = input.agent_name || '';
     if (!agentName) process.exit(0);

     if (!/^dc-/.test(agentName)) process.exit(0);

     writeHookOutput({
       hookSpecificOutput: {
         hookEventName: 'TeammateIdle',
         additionalContext: '...',
       },
     });
   } catch {
     process.exit(0);  // fail-open: any error = silent no-op
   }

   function readStdin() {
     return new Promise(resolve => {
       let data = '';
       process.stdin.on('data', chunk => { data += chunk; });
       process.stdin.on('end', () => resolve(data));
       process.stdin.on('error', () => resolve('{}'));
     });
   }

   // WRONG: No fail-open wrapper, no readStdin helper
   const input = JSON.parse(fs.readFileSync('/dev/stdin', 'utf-8'));
   ```

2) Check timeout-safe operations - no network or blocking I/O:
   ```javascript
   // CORRECT: Pure local file reads, synchronous
   import { readFileSync, existsSync } from 'node:fs';
   const state = JSON.parse(readFileSync(statePath, 'utf8'));

   // WRONG: Network call inside a hook (will timeout)
   const resp = await fetch('https://api.example.com/check');

   // WRONG: Spawning child processes from hooks
   const result = execSync('git status');
   ```

Read the full file on GitHub · 188 lines

Changes

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.

  1. 1mo ago First seen · 188 lines · 31 tokens per session scan A 836d82ea450d

Subscribe to this mod's changes

hook-safety is an agent published in the GitHub repository kangig94/coral (11 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,950 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.