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/jsohi/app-trading-engine/post-tool-usegit clone --depth 1 https://github.com/jsohi/app-trading-engineWrote 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/jsohi/app-trading-engine/post-tool-use)<a href="https://agentmods.dev/hooks/jsohi/app-trading-engine/post-tool-use"><img src="https://agentmods.dev/badge/hooks/jsohi/app-trading-engine/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
PostToolUse 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"PostToolUse": [
{
"matcher": "Agent",
"hooks": [
{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/record-plan-agent-done.sh",
"timeout": 5,
"statusMessage": "Recording Plan-agent invocation (if subagent_type=Plan)..."
}
]
},
{
"matcher": "Bash(git commit:*)",
"hooks": [
{
"type": "command",
"command": "[ \"$EXIT_CODE\" -eq 0 ] && jq -nc '{decision:\"block\", reason:\"A git commit just completed. You MUST now run ALL three test suites before pushing or doing anything else:\\n\\n 1. ./gradlew test\\n 2. ./gradlew :integration-tests:test\\n 3. ./gradlew e2e\\n\\nDo NOT skip any suite. Do NOT claim they were already run. Execute each command and report results.\"}' || exit 0",
"timeout": 5,
"statusMessage": "Enforcing post-commit test gate..."
}
]
},
{
"matcher": "Bash(git push:*)",
"hooks": [
{
"type": "command",
"command": "pr=$(gh pr view --json number -q .number 2>/dev/null); [ -n \"$pr\" ] && gh pr comment \"$pr\" --body \"@gemini review\" >/dev/null 2>&1; exit 0",
"async": true,
"timeout": 30,
"statusMessage": "Requesting Gemini review on PR..."
},
{
"type": "prompt",
"prompt": "A push just completed. You MUST now poll for Gemini review and fix all findings:\n\n1. Record PUSH_TIME=$(date -u -v-30S +%%Y-%%m-%%dT%%H:%%M:%%SZ) (30s clock-skew buffer)\n2. Wait for Gemini review: poll every 30s until gemini-code-assist[bot] review appears\n3. Fetch ALL Gemini line-level comments created after PUSH_TIME\n4. Fix ALL high, medium, and low severity findings\n5. If fixes made: run spotlessApply, commit, run all 3 test suites, push again (which triggers another Gemini round)\n6. Loop until Gemini has zero actionable comments\n\nDo NOT skip this. Do NOT say 'I already pushed'. Do NWhat else settings.json configures
This page is one entry in a file that holds 3. 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.
- 4d ago First seen · 62 lines scan A f8aadfa18c85
PostToolUse is a hook published in the GitHub repository jsohi/app-trading-engine (2 stars, last pushed 3mo 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-31.
Other hooks, from other repositories
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.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
SessionStart
Runs when a session starts, executing session-start.sh. From anthropics/claude-cookbooks.