A pre-action checkpoint that runs before the coding agent writes, edits files, or runs shell commands. It checks certain project rules before allowing the action to continue.

Use it to enforce approval rules for feature progress, detect concurrent file changes, require checks before bulk API calls, and flag repeated failing commands.

It helps stop risky or incomplete actions before they change files or affect outside services. It can also warn when commands are being repeated without success.

PreToolUse — Hook by andrewcigan

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/andrewcigan/vibe-dev-plugin/pre-tool-use

Clone the repo

git clone --depth 1 https://github.com/andrewcigan/vibe-dev-plugin

Or install vibe-dev, the plugin that ships this one along with the rest of its 29 skills, 24 agents, 7 hooks.

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

PreToolUse 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 3d 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 · 16 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Write|Edit|MultiEdit|Bash",
      "hooks": [
        {
          "type": "command",
          "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/dispatch-pre-tool-use.sh\"",
          "timeout": 15
        }
      ],
      "description": "Vibe Dev: единый PreToolUse-диспетчер. Write/Edit/MultiEdit — state-machine gate на feature_list.json (UI->passing без user-evidence = block) + concurrent-write warn. Bash — bulk-API gate (массовый внешний API без pre-launch-checklist = block) + счётчик повторов команд (инкремент здесь: PreToolUse приходит на каждый запуск; на 3-м подряд без успеха — warn про субагент-диагностику). Профили minimal/standard/strict через .harness/profile.",
      "id": "vibe:pre-tool-use"
    }
  ]
}

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.

3d ago First seen · 16 lines scan A 007d9e422ea0

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo 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.

ai-agents claude-code claude-code-plugin harness vibe-coding

PreToolUse

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

SessionStart

PostToolUse

Stop

UserPromptSubmit

SessionStart

PostToolUse