agentmods.dev

PostToolUse

PostToolUse is a hook for Claude Code from charles001-wong/autocode-flow. Its token cost is not measured, scanned A, original, MIT.

A post-action check that runs after the agent writes a file named config.json. It prints a reminder when the file belongs to an Autocode project.

In plain words
What is it for?
Use it to notice changes to Autocode config.json files and prompt the developer to run /autocode-new.
Why use it?
It helps catch configuration changes that may require regenerating pipeline files. Without it, the reminder could be easy to miss.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event.

Part of the autocode-flow plugin — 2 skills, 2 commands, 3 agents, 1 hook shipped together

not rated 2repo 6mo ago A scan tokens not measured original MIT

Good fit Use it to notice changes to Autocode config.json files and prompt the developer to run /autocode-new.

Compare 6 hooks from other repositories ↓
Install with agentmods
npx agentmods add hooks/charles001-wong/autocode-flow/post-tool-use
View source ↗ charles001-wong/autocode-flow
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.

Clone the repo
git clone --depth 1 https://github.com/charles001-wong/autocode-flow

Made for: Claude Code.

Or install autocode-flow, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 3 agents, 1 hook.

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/charles001-wong/autocode-flow/post-tool-use.svg)](https://agentmods.dev/hooks/charles001-wong/autocode-flow/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/charles001-wong/autocode-flow/post-tool-use"><img src="https://agentmods.dev/badge/hooks/charles001-wong/autocode-flow/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 6d 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.

hooks/hooks.json · 14 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "tool == \"Write\" && tool_input.file_path matches \"config\\.json$\"",
      "hooks": [
        {
          "type": "command",
          "command": "node -e \"let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{const i=JSON.parse(d);const p=i.tool_input?.file_path||'';if(p.includes('autocode')&&p.endsWith('config.json')){console.error('[autocode-flow] Config updated: '+p);console.error('[autocode-flow] Run /autocode-new to regenerate pipeline files')}console.log(d)})\""
        }
      ],
      "description": "Notify when autocode config.json is modified"
    }
  ]
}
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. 6d ago First seen · 14 lines scan A b12a52369b4b

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository charles001-wong/autocode-flow (2 stars, last pushed 6mo 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-31.

Claude Codeai-codingautomationautonomous-codingclaude-pluginpipeline
Related

Other hooks, from other repositories

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

PreToolUse

Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.

anthropics/claude-cookbooks · not measured

PreCompact

Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.

ruvnet/RuView · not measured