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/dashpot4/grok-plugin-for-claude/session-startgit clone --depth 1 https://github.com/dashpot4/grok-plugin-for-claudeWrote 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/dashpot4/grok-plugin-for-claude/session-start)<a href="https://agentmods.dev/hooks/dashpot4/grok-plugin-for-claude/session-start"><img src="https://agentmods.dev/badge/hooks/dashpot4/grok-plugin-for-claude/session-start.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
SessionStart 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 3d 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.
This is a copy
61% identical to SessionStart — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/session-lifecycle-hook.mjs\" SessionStart",
"timeout": 5
}
]
}
]
}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.
- 3d ago First seen · 13 lines scan A 9dfd63a6af72
SessionStart is a hook published in the GitHub repository dashpot4/grok-plugin-for-claude (4 stars, last pushed 1mo 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. It is 61% identical to SessionStart, differing in 6 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts, executing session-lifecycle-hook.mjs via node. From jinxlzc/grok-codex-plugin.
Stop
Runs when the agent finishes a response, executing stop-review-gate-hook.mjs via node. From jinxlzc/grok-codex-plugin.
Stop
Runs when the agent finishes a response, executing stop-review-gate-hook.mjs via node. From zachdunn/grok-plugin-claude-code.
SessionStart
Runs when a session starts, executing session-lifecycle-hook.mjs via node. From kai-wedekind/claude-code-grok-bridge.
SessionEnd
Runs when a session ends, executing session-lifecycle-hook.mjs via node. From kai-wedekind/claude-code-grok-bridge.
SessionEnd
Runs when a session ends, executing session-lifecycle-hook.mjs via node. From jinxlzc/grok-codex-plugin.