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/darkroomengineering/cc-settings/user-prompt-submitgit clone --depth 1 https://github.com/darkroomengineering/cc-settingsGrade A, and why
UserPromptSubmit 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.
What it actually says
{
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "bun \"$PLUGIN_ROOT/src/scripts/codex-hook.ts\" \"src/hooks/delegation-detector.ts\"",
"commandWindows": "bun \"%PLUGIN_ROOT%/src/scripts/codex-hook.ts\" \"src/hooks/delegation-detector.ts\"",
"timeout": 3,
"statusMessage": "Checking delegation scope"
}
]
}
]
}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 · 15 lines scan A 99f8ad89e1d4
UserPromptSubmit is a hook published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 4d 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-08-30.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for (AskUserQuestion, mcp__.*__AskUserQuestion) and Read tool calls, executing doc-read.sh (3 commands). From indykish/dotfiles.
PreToolUse
Runs before the agent uses a tool for (AskUserQuestion and mcp__.*__AskUserQuestion) tool calls, running /Users/kishore/.config/iterm2/cc-status (2 commands). From indykish/dotfiles.
Notification
Runs when the agent sends a notification, running /Users/kishore/.config/iterm2/cc-status. From indykish/dotfiles.
SessionEnd
Runs when a session ends, running /Users/kishore/.config/iterm2/cc-status. From indykish/dotfiles.
SessionStart
Runs when a session starts, running /Users/kishore/.config/iterm2/cc-status. From indykish/dotfiles.
StopFailure
Runs on the StopFailure event, running /Users/kishore/.config/iterm2/cc-status. From indykish/dotfiles.