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.
git clone --depth 1 https://github.com/DanceNitra/inspeximusWrote 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/dancenitra/inspeximus/pre-tool-use)<a href="https://agentmods.dev/hooks/dancenitra/inspeximus/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/dancenitra/inspeximus/pre-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/dancenitra/inspeximus/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/dancenitra/inspeximus/pre-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
What it actually says
{
"PreToolUse": [
{
"matcher": "Bash|Write|Edit|MultiEdit|NotebookEdit",
"hooks": [
{
"type": "command",
"command": "uvx --default-index https://pypi.org/simple --from inspeximus==3.23.0 python -E -c \"import runpy,sys;sys.path[:]=[p for p in sys.path if p not in (str(),chr(46))];runpy._run_module_as_main(sys.argv.pop(1))\" inspeximus.claude_code"
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 5. 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 Changed c8ec0e33f6c2
- 2d ago Changed e9fd0019b310
- 3d ago Changed 89fd3362406c
- 4d ago Changed 0efa9c5e75d8
- 7d ago Changed fe5347110294
- 9d ago Changed a493ba7c0842
- 10d ago Changed 92da51dafb3d
- 12d ago Changed cd7b0afd7ddc
- 14d ago Changed b59ca77c65af
- 15d ago First seen · 13 lines scan A 025d40eb2149
PreToolUse is a hook published in the GitHub repository DanceNitra/inspeximus (8 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other hooks, from other repositories
SessionStart
Runs when a session starts, running python -m wikimoth.capture.hook SessionStart. From juliangeymonat-jpg/wikimoth.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
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, 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.
PostToolUse
Runs after a tool call finishes for Bash tool calls, executing hooks.sh via sh (3 commands). From anthropics/claude-plugins-official.