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.
npx agentmods add hooks/epicsagas/epic-harness/pre-tool-usegit clone --depth 1 https://github.com/epicsagas/epic-harnessWrote 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.
[](https://agentmods.dev/hooks/epicsagas/epic-harness/pre-tool-use)<a href="https://agentmods.dev/hooks/epicsagas/epic-harness/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/epicsagas/epic-harness/pre-tool-use.svg" alt="Measured on agentmods" height="20"></a>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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"description": "Block dangerous commands (force push, prod DB drop, rm -rf /)" What it actually says
{
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "EH=$(command -v epic 2>/dev/null); test -n \"$EH\" && \"$EH\" guard || echo '[harness] epic not found, skipping guard'",
"timeout": 5
}
],
"description": "Block dangerous commands (force push, prod DB drop, rm -rf /)"
}
]
}What else hooks.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 15 lines scan C 2e3eb88b5268
PreToolUse is a hook published in the GitHub repository epicsagas/epic-harness (18 stars, last pushed today), licensed Apache-2.0. 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-09-04.
Other hooks, from other repositories
SessionStart
Runs when a session starts, executing session-start.sh. From HKUDS/LightRAG.
SubagentStop
Runs when a subagent finishes, executing retention_guard.py via python3. From MythicAgents/sage.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.