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/go-to-k/cdkd/post-tool-usegit clone --depth 1 https://github.com/go-to-k/cdkdGrade 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 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
{
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "jq -r '.tool_input.file_path // .tool_response.filePath' | { read -r f; echo \"$f\" | grep -qE '\\.(ts|tsx)$' && vp run lint:fix; } 2>/dev/null || true",
"timeout": 30,
"statusMessage": "Running lint:fix..."
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/post-merge-sync-reminder.sh",
"timeout": 5,
"statusMessage": "Post-merge sync reminder check"
},
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/main-tree-dirty-detector.sh",
"timeout": 10,
"statusMessage": "Checking main-tree tracked-file dirtiness..."
},
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/main-tree-git-cwd-detector.sh",
"timeout": 10,
"statusMessage": "Checking for main-tree git cwd-race..."
}
]
}
]
}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 · 38 lines scan A 143e520d33a7
PostToolUse is a hook published in the GitHub repository go-to-k/cdkd (122 stars, last pushed yesterday), 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 Bash tool calls, running an inline shell check. From hoangsonww/WealthWise-Finance-Tracker.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, running an inline shell check. From hoangsonww/WealthWise-Finance-Tracker.
SessionStart
Runs when a session starts, executing session-start.sh. From wewpellex21/code-sensei.
SessionEnd
Runs when a session ends, executing session-stop.sh. From wewpellex21/code-sensei.
PostToolUse
Runs after a tool call finishes for Write, Edit, MultiEdit and Bash tool calls, executing track-code-change.sh and track-command.sh (2 commands). From wewpellex21/code-sensei.
SessionStart
Runs when a session starts, executing session-banner.sh via bash. From anmolnagpal/devops-skills.