Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamtouchskyer/memex/plugin install 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/session-start)<a href="https://agentmods.dev/hooks/iamtouchskyer/memex/session-start"><img src="https://agentmods.dev/badge/hooks/iamtouchskyer/memex/session-start/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/session-start"><img src="https://agentmods.dev/badge/hooks/iamtouchskyer/memex/session-start.svg" alt="Reviewed on agentmods" width="80" 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 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.
How it starts
The opening of the file, as written. The whole thing — 13 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"SessionStart": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "MEMEX_CLI_PATH=\"${CLAUDE_PLUGIN_ROOT}/dist/cli.js\"; if [ ! -f \"$MEMEX_CLI_PATH\" ]; then echo '## Memex: plugin dist not found\n\nReinstall the memex Claude Code plugin or run: `npm install -g @touchskyer/memex`'; exit 0; fi && node \"$MEMEX_CLI_PATH\" sync 2>/dev/null; TOTAL=$(node \"$MEMEX_CLI_PATH\" read index 2>/dev/null | grep -c '^\\- \\[\\[' || true); SECTIONS=$(node \"$MEMEX_CLI_PATH\" read index 2>/dev/null | awk '/^## /{ if(s) print s\" (\"c\" cards)\"; s=$0; c=0; next } /^\\- \\[\\[/{ c++ } END{ if(s) print s\" (\"c\" cards)\" }'); if [ \"$TOTAL\" -gt 0 ]; then RECALL=\"When the task touches a topic above, run \\`memex search <keyword>\\` then \\`memex read <slug>\\` for the top hits.\nDo this BEFORE writing code or starting diagnosis — your past self already solved adjacent problems.\nFor full recall: invoke the \\`memex-recall\\` skill.\"; else RECALL=\"No cards yet. Still invoke the \\`memex-recall\\` skill — keyword search may find matches even without an index.\nAfter completing work, invoke \\`memex-retro\\` to start building your knowledge base.\"; fi; echo \"## Memex Memory System Active ($TOTAL cards)\n\n### Your Knowledge Map\n$SECTIONS\n\n### Recall — before starting work\n$RECALL\nNever include actual secrets, credentials, tokens, or exact secret file contents in memex query/body arguments; use abstract descriptions or redacted examples.\n\n### Retro — after completing work\nAfter code changes, debugging, or architectural decisions: invoke \\`memex-retro\\` skill.\nAsk: 'Did I learn something reusable?' If yes, write a card.\nCard format: title, created (YYYY-MM-DD), source: retro, category. Slugs: English kebab-case.\nLanguage: match the user's CLAUDE.md preferences.\" && last_org=$(cat ~/.memex/.last-organize 2>/dev/null || true) && if [ -n \"$last_org\" ]; then days_since=$(( ($(date +%s) - $(python3 -c \"import 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 e255b580037b
SessionStart 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 on startup, clear and compact, running leteo hook session-start (2 commands). From asanabrial/leteo.
PreCompact
Runs before the context is compacted, running npx hipocampus compact --stdin. From kevin-hs-sohn/hipocampus.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.