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.
git clone --depth 1 https://github.com/iamtouchskyer/memexWrote 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/iamtouchskyer/memex/stop)<a href="https://agentmods.dev/hooks/iamtouchskyer/memex/stop"><img src="https://agentmods.dev/badge/hooks/iamtouchskyer/memex/stop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/iamtouchskyer/memex/stop"><img src="https://agentmods.dev/badge/hooks/iamtouchskyer/memex/stop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
Stop 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 1mo 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
{
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "echo '## 🧠 Memex Retro Reminder\n\n**MANDATORY**: If this task involved code changes, architectural decisions, debugging, or non-trivial problem solving, you MUST invoke the \\`memex-retro\\` skill NOW before ending your turn.\n\nDid you learn something reusable? Capture it as a knowledge card. Do not include actual secrets, credentials, tokens, or exact secret file contents.\n\n**Skip retro only if**: This was purely informational (no problem solving) or you already captured insights during the session.'"
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 13 lines scan A 096832587ca6
Stop is a hook published in the GitHub repository iamtouchskyer/memex (144 stars, last pushed 1mo 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
SessionStart
Runs when a session starts, running memorix hook. From AVIDS2/memorix.
PostToolUse
Runs after a tool call finishes, running memorix hook. From AVIDS2/memorix.
Stop
Runs when the agent finishes a response, executing stop.sh via bash. From kage-core/Kage.
SubagentStop
Runs when a subagent finishes, executing observe.sh via bash. From kage-core/Kage.
SessionEnd
Runs when a session ends, executing observe.sh via bash. From kage-core/Kage.
PreCompact
Runs before the context is compacted, running an inline shell check. From nickroci/ultan.