agentmods.dev

PostToolUse

PostToolUse is a hook for Claude Code from oliver-kriska/claude-elixir-phoenix. Its token cost is not measured, scanned A, original, MIT.

A set of automatic actions that run after editing or writing files in an Elixir or Phoenix project. These actions format code, check project rules, warn about debugging statements, remind about plans and security, and record progress.

In plain words
What is it for?
Use it to automatically format Elixir files, verify project-specific rules, flag debug statements, show plan or security reminders, and log work after edits.
Why use it?
It catches routine issues immediately after file changes and keeps related development checks from being forgotten.

Hook for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the phx plugin — 50 skills, 26 agents, 10 hooks shipped together

One of 10 entries in hooks.json upstream. Installing this one merges just its entry into your config; the other 9 are separate, each on its own page.

not rated 539repo +1 2d ago A scan tokens not measured original MIT

Good fit Use it to automatically format Elixir files, verify project-specific rules, flag debug statements, show plan or security reminders, and log work after edits.

Compare 6 hooks from other repositories ↓
View source ↗ oliver-kriska/claude-elixir-phoenix phxagents.dev
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add oliver-kriska/claude-elixir-phoenix
Claude Code
/plugin install phx

Made for: Claude Code.

Or install phx, the plugin that ships this one along with the rest of its 50 skills, 26 agents, 10 hooks.

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 PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/oliver-kriska/claude-elixir-phoenix/post-tool-use.svg)](https://agentmods.dev/hooks/oliver-kriska/claude-elixir-phoenix/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/oliver-kriska/claude-elixir-phoenix/post-tool-use"><img src="https://agentmods.dev/badge/hooks/oliver-kriska/claude-elixir-phoenix/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

PostToolUse 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 8d 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.

plugins/elixir-phoenix/hooks/hooks.json · 107 lines

How it starts

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

{
  "PostToolUse": [
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "if": "Edit(*.ex)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/format-elixir.sh",
          "timeout": 30,
          "statusMessage": "Formatting Elixir..."
        },
        {
          "type": "command",
          "if": "Edit(*.exs)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/format-elixir.sh",
          "timeout": 30,
          "statusMessage": "Formatting Elixir..."
        },
        {
          "type": "command",
          "if": "Edit(*.ex)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/iron-law-verifier.sh",
          "timeout": 15,
          "statusMessage": "Verifying Iron Laws..."
        },
        {
          "type": "command",
          "if": "Edit(*.exs)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/iron-law-verifier.sh",
          "timeout": 15,
          "statusMessage": "Verifying Iron Laws..."
        },
        {
          "type": "command",
          "if": "Edit(*.ex)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/debug-statement-warning.sh",
          "timeout": 15,
          "statusMessage": "Checking for debug statements..."
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "if": "Write(*.ex)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/format-elixir.sh",
          "timeout": 30,
          "statusMessage": "Formatting Elixir..."
        },
        {
          "type": "command",
          "if": "Write(*.exs)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/format-elixir.sh",
          "timeout": 30,
          "statusMessage": "Formatting Elixir..."
        },
        {
          "type": "command",
          "if": "Write(*.ex)",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/iron-law-verifier.sh",
          "timeout": 15,
          "statusMessage": "V

Read the full file on GitHub · 107 lines

Same file

What else hooks.json configures

This page is one entry in a file that holds 10. Installing the file brings all of them; each is measured and scanned on its own page.

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. 8d ago First seen · 107 lines scan A 9f431bcd9521

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository oliver-kriska/claude-elixir-phoenix (539 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Codeautomationclaudeclaude-code-pluginclaude-code-skillsclaude-skills
Related

Other hooks, from other repositories

PreToolUse

Runs before the agent uses a tool for Bash tool calls, executing run-hook.cmd. From omas-odoo/odoo-superpowers.

omas-odoo/odoo-superpowers · not measured

PostToolUse

Runs after a tool call finishes for Edit and Write tool calls, executing run-hook.cmd. From assoumaaa/odoo-superpowers.

assoumaaa/odoo-superpowers · not measured

PostToolUse

Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.

supabase/supabase · not measured

SessionStart

Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.

supabase/supabase · not measured

SessionStart

Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.

google-gemini/gemini-cli · not measured

PreToolUse

Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.

apache/superset · not measured