Commands that run before the agent reads, writes, edits files, or enters planning mode. They execute project-provided shell scripts from ArchCodex.

Running pre-action checks before file creation, modification, or reading, and before the agent starts a plan. The input does not explain what each script checks.

They can apply the project's checks and reminders before those actions happen, helping guide or restrict how the agent changes and reads code.

PreToolUse — Hook by ArchCodexOrg

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/archcodexorg/archcodex/pre-tool-use

Clone the repo

git clone --depth 1 https://github.com/ArchCodexOrg/archcodex

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

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "command": ".claude/hooks/archcodex-pre-write.sh"
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": ".claude/hooks/archcodex-reminder.sh"
        }
      ]
    },
    {
      "matcher": "Read",
      "hooks": [
        {
          "type": "command",
          "command": ".claude/hooks/archcodex-pre-read.sh"
        }
      ]
    },
    {
      "matcher": "EnterPlanMode",
      "hooks": [
        {
          "type": "command",
          "command": ".claude/hooks/archcodex-plan-mode.sh"
        }
      ]
    }
  ]
}

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 · 40 lines scan A 1b3f90260fb8

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository ArchCodexOrg/archcodex (5 stars, last pushed 3mo 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.

Data and AI LLM Planning architecture cli coding-agents mcp spec

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

Stop

PostToolUse

UserPromptSubmit

PreToolUse

SessionEnd