PostToolUseFailure

PostToolUseFailure is a hook for coding agents from xiaobei930/cc-best. Its token cost is not measured, scanned A, original, MIT.

A failure hook that runs after another tool call fails. A hook is an automatic action triggered by an event in an agent workflow.

In plain words
What is it for?
Use it to trigger post-failure tracking whenever a tool reports an error.
Why use it?
It records tool failures and checks for repeated error patterns, making recurring problems easier to notice. The input does not describe any further repair behavior.

Hook

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 cc-best plugin — 19 skills, 44 commands, 8 agents, 20 hooks shipped together

One of 20 entries in hooks.json — they are configured in one file and arrive together.

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 xiaobei930/cc-best
Claude Code
/plugin install cc-best

Or install cc-best, the plugin that ships this one along with the rest of its 19 skills, 44 commands, 8 agents, 20 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 PostToolUseFailure

README.md
[![agentmods](https://agentmods.dev/badge/hooks/xiaobei930/cc-best/post-tool-use-failure.svg)](https://agentmods.dev/hooks/xiaobei930/cc-best/post-tool-use-failure)
Your own site
<a href="https://agentmods.dev/hooks/xiaobei930/cc-best/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/xiaobei930/cc-best/post-tool-use-failure.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. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

PostToolUseFailure 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 5d 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 · 15 lines

What it actually says

{
  "PostToolUseFailure": [
    {
      "matcher": ".*",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/node/hooks/post-tool-failure.js\"",
          "timeout": 3
        }
      ],
      "description": "失败追踪: 工具调用失败后记录错误模式,检测重复失败(红旗增强)"
    }
  ]
}
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. 5d ago First seen · 15 lines scan A fc2a81fb0a54

Subscribe to this mod's changes

PostToolUseFailure is a hook published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo 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.