agentmods.dev

PostToolUse

An automatic formatting hook that runs after files are written or edited.

In plain words
What is it for?
Use it to run `bun x ultracite fix` after Write or Edit operations.
Why use it?
It keeps changed code formatted without requiring a separate manual formatting step.

Hook for Claude Code

277 5mo ago A scan tokens not measured original MIT
View the source file axeldelafosse/loop
Install

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.

agentmods
npx agentmods add hooks/axeldelafosse/loop/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/axeldelafosse/loop

Made for: Claude Code.

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. Scan, not verified.
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 yesterday.

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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.claude/settings.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "bun x ultracite fix"
        }
      ]
    }
  ]
}
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. yesterday First seen · 13 lines scan A 1f6ed1a91d4e

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository axeldelafosse/loop (277 stars, last pushed 5mo 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.

bunclaudeclaude-codeclaude-code-channelscodexcodex-cli
Related

Other hooks, from other repositories

SessionStart

Runs when a session starts, running trce spool --harness codex-cli --event SessionStart. From assimovt/trce-cli.

assimovt/trce-cli · not measured

UserPromptSubmit

Runs when you submit a prompt, before the agent sees it, running trce spool --harness codex-cli --event UserPromptSubmit. From assimovt/trce-cli.

assimovt/trce-cli · not measured

PostCompact

Runs after the context is compacted, running trce spool --harness codex-cli --event PostCompact. From assimovt/trce-cli.

assimovt/trce-cli · not measured

PreToolUse

Runs before the agent uses a tool for Bash, apply_patch, spawn_agent and multi_agent_v1.spawn_agent tool calls, executing bin.mjs via bun (3 commands). From fusengine/codex.

fusengine/codex · not measured

PostToolUse

Runs after a tool call finishes for apply_patch, context7, exa, Bash and update_plan tool calls, executing bin.mjs via bun (3 commands). From fusengine/codex.

fusengine/codex · not measured

UserPromptSubmit

Runs when you submit a prompt, before the agent sees it, executing bin.mjs via bun. From fusengine/codex.

fusengine/codex · not measured