PreToolUse

Pre-tool checks that run before the agent writes files, edits files, or executes shell commands. They validate project state and inspect commands for dangerous operations.

In plain words
What is it for?
Use them to guard files such as execution records, check stage status, and intercept commands such as recursive deletion, forced Git pushes, or database table removal.
Why use it?
They reduce the chance of invalid artifact changes or destructive shell commands running by mistake.

Hook for Claude Code

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/echovic/boss-skill/pre-tool-use
Clone the repo
git clone --depth 1 https://github.com/echoVic/boss-skill

Made for: Claude Code.

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 C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade C, and why

PreToolUse scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"description": "Intercept dangerous shell commands (rm -rf, git push --force, DROP TABLE, etc.)",
.claude/settings.json · 28 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "boss hooks run \"pre:write:artifact-guard\" \"scripts/hooks/pre-tool-write.js\" \"standard,strict\"",
          "timeout": 5
        }
      ],
      "description": "Protect execution.json and validate stage status before artifact writes",
      "id": "pre:write:artifact-guard"
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "boss hooks run \"pre:bash:dangerous-cmd-guard\" \"scripts/hooks/pre-tool-bash.js\" \"standard,strict\"",
          "timeout": 5
        }
      ],
      "description": "Intercept dangerous shell commands (rm -rf, git push --force, DROP TABLE, etc.)",
      "id": "pre:bash:dangerous-cmd-guard"
    }
  ]
}
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. 2d ago First seen · 28 lines scan C d3052f6ad2fd

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.