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/rmarquesa/agentmemory-offline/notificationgit clone --depth 1 https://github.com/rmarquesa/agentmemory-offlineGrade A, and why
Notification 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.
This is a copy
50% identical to SessionStart — 7 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
{
"Notification": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/notification.mjs\""
}
]
}
]
}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 · 12 lines scan A 39bbfd787b24
Notification is a hook published in the GitHub repository rmarquesa/agentmemory-offline (0 stars, last pushed 2d 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 50% identical to SessionStart, differing in 7 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup, resume, clear and compact, executing paxm-hook.sh via sh. From pax-beehive/paxm.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing paxm-hook.sh via sh. From pax-beehive/paxm.
PostToolUse
Runs after a tool call finishes, executing paxm-hook.sh via sh. From pax-beehive/paxm.
PostToolUseFailure
Runs when a tool call fails, executing paxm-hook.sh via sh. From pax-beehive/paxm.
Stop
Runs when the agent finishes a response, executing paxm-hook.sh via sh. From pax-beehive/paxm.
SessionStart
Runs when a session starts, executing session-start-manifest.js via node. From palimem/palimem.