PostToolUse

PostToolUse is a hook for Claude Code from cacr92/WeReply. Its token cost is not measured, scanned A, original, MIT.

A set of automatic checks that run after files are written or edited. It targets Rust files and frontend TypeScript files, then runs commands such as Clippy checks and type-binding generation.

In plain words
What is it for?
Use it to run Rust linting, regenerate bindings, and check frontend files for console statements after code changes.
Why use it?
It catches some code-quality issues and keeps generated type bindings updated immediately after relevant edits.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event.

One of 8 entries in settings.json — they are configured in one file and arrive together.

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/cacr92/wereply/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/cacr92/WeReply

Made for: Claude Code.

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

.claude/settings.json · 67 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write.*\\.rs$|Edit.*\\.rs$",
      "hooks": [
        {
          "type": "command",
          "command": "echo 🔍 Rust 代码规范检查..."
        },
        {
          "type": "command",
          "command": "cargo clippy --quiet 2>&1 | grep -E 'warning|error' | head -n 10 || echo ✅ Clippy检查通过",
          "timeout": 45
        },
        {
          "type": "command",
          "command": "echo 🔄 更新类型绑定..."
        },
        {
          "type": "command",
          "command": "cargo run --bin generate_bindings --quiet 2>&1 || echo ⚠️ 类型绑定生成失败,请手动运行 cargo run --bin generate_bindings",
          "timeout": 30
        },
        {
          "type": "command",
          "command": "echo ✅ Rust 文件处理完成"
        }
      ]
    },
    {
      "matcher": "Write.*frontend.*\\.(ts|tsx)$|Edit.*frontend.*\\.(ts|tsx)$",
      "hooks": [
        {
          "type": "command",
          "command": "echo 🔍 TypeScript 代码规范检查..."
        },
        {
          "type": "command",
          "command": "jq -r '.tool_input.file_path' | { read file_path; grep -n 'console\\.\\(log\\|error\\|warn\\)' \"$file_path\" 2>/dev/null && echo '⚠️ 检测到 console 日志!请使用 message 组件'; grep -n 'as any' \"$file_path\" 2>/dev/null && echo '⚠️ 检测到 as any!请使用精确类型'; true; }"
        },
        {
          "type": "command",
          "command": "cd frontend && npx tsc --noEmit --pretty 2>&1 | head -n 20 || echo ✅ TypeScript类型检查通过",
          "timeout": 20
        },
        {
          "type": "command",
          "command": "cd frontend && npm run lint --silent 2>&1 | head -n 10 || echo ✅ ESLint检查通过",
          "timeout": 25
        },
        {
          "type": "command",
          "command": "echo ✅ TypeScript 文件处理完成"
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "echo 📝 记得更新 CHANGELOG.md"
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 8. Installing the file brings all of them; each is measured and scanned on its own page.

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 · 67 lines scan A dcb656ed9f2e

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo 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.