UserPromptSubmit

A prompt-submission hook that runs several shell checks before the coding agent sees a user's message. The checks look for continuation requests, future intents, automatic mode, and power tools.

In plain words
What is it for?
Use it to trigger project checks whenever a user submits a prompt.
Why use it?
It catches relevant project state at the start of each request instead of relying on the agent to remember to check it. The provided details do not explain what each check changes.

Hook

Part of the plastic plugin — 43 skills, 10 agents, 5 hooks, 1 MCP server shipped together

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/zalom/plastic/user-prompt-submit
Clone the repo
git clone --depth 1 https://github.com/zalom/plastic

Or install plastic, the plugin that ships this one along with the rest of its 43 skills, 10 agents, 5 hooks, 1 MCP server.

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 64% copy Near-identical to another mod 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 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.

Origin

This is a copy

64% identical to SessionStart — 39 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.

hooks/hooks.json · 44 lines

What it actually says

{
  "UserPromptSubmit": [
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" continue",
          "statusMessage": "Checking for continue..."
        }
      ]
    },
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/future-intent-check\"",
          "statusMessage": "Checking future intents..."
        }
      ]
    },
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/auto-arm\"",
          "statusMessage": "Checking auto mode..."
        }
      ]
    },
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" power-tools",
          "statusMessage": "Checking power tools..."
        }
      ]
    }
  ]
}
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. 3d ago First seen · 44 lines scan A 47e7f941c62f

Subscribe to this mod's changes

UserPromptSubmit is a hook published in the GitHub repository zalom/plastic (10 stars, last pushed 3d 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. It is 64% identical to SessionStart, differing in 39 lines, and is treated as a copy.