A check that runs before a coding agent uses the Bash command tool and can modify the command to pass it through the project’s command wrapper.

It helps enforce the project’s Bash-command handling before commands run, while skipping commands that already use the wrapper or match excluded patterns.

It applies the wrapper automatically to eligible shell commands, so the agent does not need to add it by hand each time.

PreToolUse — Hook by mblua

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/mblua/agentscommander/pre-tool-use

Clone the repo

git clone --depth 1 https://github.com/mblua/AgentsCommander

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 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 yesterday.

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 · 13 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "node -e \"'@ac-rtk-marker-v2';const s=JSON.parse(require('fs').readFileSync(0,'utf8'));const c=s?.tool_input?.command;if(!c){process.exit(0)}if(/^rtk\\s/.test(c)||/&&\\s*rtk\\s/.test(c)){process.exit(0)}const skip=/^(cd |mkdir |echo |cat <<|source |export |\\.|set )/.test(c);if(skip){process.exit(0)}const parts=c.split(/\\s*(&&|\\|\\||;)\\s*/);const out=parts.map((p,i)=>{if(i%2===1)return p;if(/^rtk\\s/.test(p))return p;return 'rtk '+p}).join(' ');if(out!==c){console.log(JSON.stringify({hookSpecificOutput:{hookEventName:'PreToolUse',updatedInput:{...s.tool_input,command:out}}}))}else{process.exit(0)}\""
        }
      ]
    }
  ]
}

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.

yesterday First seen · 13 lines scan A 069fe6a73d83

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository mblua/AgentsCommander (10 stars, last pushed yesterday), 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.

Languages ai-agents claude-code developer-tools rust solidjs tauri

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

PostToolUse

PreToolUse

PreToolUse

PreToolUse

PostToolUse

Stop