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/rasputinkaiser/self-improvement-plugin/post-tool-usegit clone --depth 1 https://github.com/RasputinKaiser/Self-Improvement-PluginGrade 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 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
{
"PostToolUse": [
{
"matcher": "Edit|Write|MultiEdit",
"hooks": [
{
"type": "command",
"command": "python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/hook_event_tap.py --event PostToolUse --script script_smoke.py -- python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/script_smoke.py",
"timeout": 7,
"statusMessage": "Script smoke"
},
{
"type": "command",
"command": "python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/hook_event_tap.py --event PostToolUse --script escalation_advisor.py -- python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/escalation_advisor.py",
"timeout": 8,
"statusMessage": "Escalation advisor"
},
{
"type": "command",
"command": "python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/hook_event_tap.py --event PostToolUse --script sips_presence_mirror.py -- python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/sips_presence_mirror.py || true",
"timeout": 7,
"statusMessage": "SIPS mirror"
},
{
"type": "command",
"command": "python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/hook_event_tap.py --event PostToolUse --script retry_lesson_reminder.py -- python3 \"${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\"/scripts/retry_lesson_reminder.py",
"timeout": 8,
"statusMessage": "Retry lesson reminder"
}
]
}
]
}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 · 33 lines scan A 9679219ee09d
PostToolUse is a hook published in the GitHub repository RasputinKaiser/Self-Improvement-Plugin (6 stars, last pushed 5d 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-31.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for Edit, Write, NotebookEdit and Skill tool calls, executing post-edit-format.sh and post-skill-auto-loop.sh (2 commands). From sd0xdev/sd0x-harness.
SubagentStop
Runs when a subagent finishes, executing cc10x_event_logger.py via python3. From romiluz13/cc10x.
StopFailure
Runs on the StopFailure event, executing cc10x_event_logger.py via python3. From romiluz13/cc10x.
PermissionRequest
Runs when the agent asks permission for an action, executing dev-hook.mjs with --hook. From FailproofAI/failproofai.
PermissionDenied
Runs on the PermissionDenied event, executing dev-hook.mjs with --hook. From FailproofAI/failproofai.
ConfigChange
Runs on the ConfigChange event, executing dev-hook.mjs with --hook. From FailproofAI/failproofai.