agentmods.dev

PostToolUse

A set of automatic actions that run after editing files or using shell commands. These actions update a code graph and record edits, shell-based writes, file moves, and Git operations.

In plain words
What is it for?
Use it to maintain the project's code-relationship graph and activity records when files are edited, written, moved, or changed through shell commands.
Why use it?
It keeps project tracking information current after changes, reducing the need to remember separate bookkeeping steps.

Hook for Claude Code

92 3d ago A scan tokens not measured copy · 94% Apache-2.0
View the source file optave/ops-codegraph-tool
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/optave/ops-codegraph-tool/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/optave/ops-codegraph-tool

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 94% copy Near-identical to another mod 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

This is a copy

94% identical to PreToolUse — 59 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.

.claude/settings.json · 39 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "p=\"${CLAUDE_PROJECT_DIR}\"; [ -d \"$p/.claude/hooks\" ] || p=\"$(git rev-parse --show-toplevel 2>/dev/null)\"; [ -d \"$p/.claude/hooks\" ] || exit 0; bash \"$p/.claude/hooks/update-graph.sh\"",
          "timeout": 30
        },
        {
          "type": "command",
          "command": "p=\"${CLAUDE_PROJECT_DIR}\"; [ -d \"$p/.claude/hooks\" ] || p=\"$(git rev-parse --show-toplevel 2>/dev/null)\"; [ -d \"$p/.claude/hooks\" ] || exit 0; bash \"$p/.claude/hooks/track-edits.sh\"",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "p=\"${CLAUDE_PROJECT_DIR}\"; [ -d \"$p/.claude/hooks\" ] || p=\"$(git rev-parse --show-toplevel 2>/dev/null)\"; [ -d \"$p/.claude/hooks\" ] || exit 0; bash \"$p/.claude/hooks/track-bash-writes.sh\"",
          "timeout": 5
        },
        {
          "type": "command",
          "command": "p=\"${CLAUDE_PROJECT_DIR}\"; [ -d \"$p/.claude/hooks\" ] || p=\"$(git rev-parse --show-toplevel 2>/dev/null)\"; [ -d \"$p/.claude/hooks\" ] || exit 0; bash \"$p/.claude/hooks/track-moves.sh\"",
          "timeout": 5
        },
        {
          "type": "command",
          "command": "p=\"${CLAUDE_PROJECT_DIR}\"; [ -d \"$p/.claude/hooks\" ] || p=\"$(git rev-parse --show-toplevel 2>/dev/null)\"; [ -d \"$p/.claude/hooks\" ] || exit 0; bash \"$p/.claude/hooks/post-git-ops.sh\"",
          "timeout": 30
        }
      ]
    }
  ]
}
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 · 39 lines scan A ed00c8df7075

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed 3d ago), licensed Apache-2.0. 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 94% identical to PreToolUse, differing in 59 lines, and is treated as a copy.

Git and workflowResearchai-agentsclicode-analysisdependency-graphimpact-analysisincremental-builds
Related

Other hooks, from other repositories

PreToolUse

Runs before the agent uses a tool for Read, Grep, Glob and Bash tool calls, executing scala-semantic-guard.sh. From MercurieVV/ScalaSemantic.

MercurieVV/ScalaSemantic · not measured

PreToolUse

Runs before the agent uses a tool for Read, Edit, Write, MultiEdit, NotebookEdit, Bash, Grep and Glob tool calls, executing pre-tool-use.js and report-gate-hook.js via node (11 commands). From ch015/code-pentester.

ch015/code-pentester · not measured

Stop

Runs when the agent finishes a response, executing on-stop.js via node. From ch015/code-pentester.

ch015/code-pentester · not measured

PostToolUse

Runs after a tool call finishes for Edit, Write, MultiEdit and NotebookEdit tool calls, running sh "$CLAUDE_PROJECT_DIR/scripts/hook-check". From GhostlyGawd/codeweb.

GhostlyGawd/codeweb · not measured

PreToolUse

Runs before the agent uses a tool for Edit, Write, MultiEdit and NotebookEdit tool calls, running python3 "$CLAUDE_PROJECT_DIR/scripts/hook-protect". From GhostlyGawd/codeweb.

GhostlyGawd/codeweb · not measured

PostToolUse

Runs after a tool call finishes, running whyline-hook. From anishmoncivarghese/sonde.

anishmoncivarghese/sonde · not measured