A set of automatic actions that run after another tool call finishes. These actions track plans and execution tasks and record tool costs using scripts run through uv, a Python package and command runner.

Use it to maintain Contextune plan and execution tracking and collect information about tool costs after commands or other tool calls.

It keeps project tracking and tool-use records updated without requiring a separate manual step after each tool call.

PostToolUse — Hook by shakestzd

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/shakestzd/contextune/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/shakestzd/contextune

Or install contextune, the plugin that ships this one along with the rest of its 8 skills, 14 commands, 5 agents, 6 hooks, 1 MCP server.

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 2d 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 · 27 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "*",
      "hooks": [
        {
          "type": "command",
          "command": "uv run ${CLAUDE_PLUGIN_ROOT}/hooks/contextune_plan_tracker.py",
          "timeout": 3000,
          "description": "Auto-create HtmlGraph track from /ctx:plan"
        },
        {
          "type": "command",
          "command": "uv run ${CLAUDE_PLUGIN_ROOT}/hooks/contextune_execute_tracker.py",
          "timeout": 3000,
          "description": "Auto-create HtmlGraph features from /ctx:execute tasks"
        },
        {
          "type": "command",
          "command": "uv run ${CLAUDE_PLUGIN_ROOT}/hooks/tool_cost_tracker.py",
          "timeout": 2000,
          "description": "Track tool costs and optimization opportunities"
        }
      ]
    }
  ]
}

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.

2d ago First seen · 27 lines scan A 4df93ddae509

Subscribe to this mod's changes

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

Cost Optimization ai-assistant automation claude-code context-engineering git-worktrees

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

SessionEnd

StopFailure

Stop

PreCompact

PreCompact

UserPromptSubmit