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/alibaba/anolisa/pre-tool-usegit clone --depth 1 https://github.com/alibaba/anolisaGrade 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 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.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- UserPromptSubmit — 89% identical, 27 lines differ
- PostToolUse — 89% identical, 19 lines differ
What it actually says
{
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "python3 ${PLUGIN_ROOT}/hooks/code_scanner_hook.py",
"timeout": 10,
"statusMessage": "Scanning command for security issues..."
}
]
},
{
"hooks": [
{
"type": "command",
"command": "python3 ${PLUGIN_ROOT}/hooks/observability_hook.py",
"timeout": 10
},
{
"type": "command",
"command": "python3 ${PLUGIN_ROOT}/hooks/pii_checker_hook.py",
"timeout": 10,
"statusMessage": "Checking for PII in tool input..."
}
]
}
]
}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.
- 2d ago First seen · 30 lines scan A ddf34a08d350
PreToolUse is a hook published in the GitHub repository alibaba/anolisa (614 stars, last pushed 3d ago), 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for AskUserQuestion, mcp__.*, Write, Edit and MultiEdit tool calls, executing free-text-guard.sh, external-operation-gate.js and duplicate-build-start-gate.js via bash (3 commands). From JKHeadley/instar.
SessionStart
Runs when a session starts on startup, resume and compact, executing session-start.sh via bash (3 commands). From JKHeadley/instar.
Stop
Runs when the agent finishes a response, executing hook-event-reporter.js and build-stop-hook.sh via node (2 commands). From JKHeadley/instar.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing telegram-topic-context.sh via bash. From JKHeadley/instar.
PostToolUse
Runs after a tool call finishes, executing hook-event-reporter.js via node. From JKHeadley/instar.
PermissionRequest
Runs when the agent asks permission for an action, executing auto-approve-permissions.js via node. From JKHeadley/instar.