UserPromptSubmit

Prompt-triggered memory hooks run before the coding agent sees your message when it matches patterns such as asking about conventions, recalling information, reviewing work, or making changes.

In plain words
What is it for?
They support prompts about preferred practices, past decisions, reviews, research, implementation, fixes, and other project work.
Why use it?
They help the agent look up relevant saved project context before responding, reducing repeated explanations and forgotten decisions.

Hook

Install

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.

agentmods
npx agentmods add hooks/scitrera/memorylayer/user-prompt-submit
Clone the repo
git clone --depth 1 https://github.com/scitrera/memorylayer
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

UserPromptSubmit 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 yesterday.

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.

memorylayer-cc-plugin/hooks/hooks.json · 54 lines

What it actually says

{
  "UserPromptSubmit": [
    {
      "matcher": ".*\\b(which\\s+\\w+\\s+should|should\\s+we\\s+use|what\\s+do\\s+we\\s+use|how\\s+do\\s+we|what'?s\\s+our|preferred|convention|do\\s+we\\s+have\\s+a|what'?s\\s+the\\s+(default|standard|preferred))\\b.*",
      "hooks": [
        {
          "type": "command",
          "command": "memorylayer-hook UserPromptSubmit",
          "timeout": 8000
        }
      ]
    },
    {
      "matcher": ".*\\b(remember|recall|what did we|how did we|remind me|what was the|what were the|what do you (know|remember))\\b.*",
      "hooks": [
        {
          "type": "command",
          "command": "memorylayer-hook UserPromptSubmit",
          "timeout": 8000
        }
      ]
    },
    {
      "matcher": ".*\\b(review|assess|analyze|evaluate|audit|investigate|explore|research|compare|status|state of|readiness|gap analysis)\\b.*",
      "hooks": [
        {
          "type": "command",
          "command": "memorylayer-hook UserPromptSubmit",
          "timeout": 8000
        }
      ]
    },
    {
      "matcher": ".*\\b(implement|build|create|add|fix|refactor|update|change|modify)\\b.*",
      "hooks": [
        {
          "type": "command",
          "command": "memorylayer-hook UserPromptSubmit",
          "timeout": 8000
        }
      ]
    },
    {
      "matcher": ".*\\b(error|bug|issue|broken|failing|crash|exception|doesn't work|not working)\\b.*",
      "hooks": [
        {
          "type": "command",
          "command": "memorylayer-hook UserPromptSubmit",
          "timeout": 8000
        }
      ]
    }
  ]
}
Changes

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.

  1. yesterday First seen · 54 lines scan A e653996e0d89

Subscribe to this mod's changes

UserPromptSubmit is a hook published in the GitHub repository scitrera/memorylayer (2 stars, last pushed 3mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.