An automatic action that runs after a Bash tool call finishes, where Bash is a command-line tool used to run shell commands. This one checks whether changes were staged with Git, a version-control system.

Watching completed Bash commands for Git staging actions and displaying a reminder to run the project’s commit-message command.

It reminds the developer to create a commit message after files are prepared for committing. That prevents staged changes from being left without the next version-control step.

PostToolUse — Hook by ndisisnd

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/ndisisnd/msg/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/ndisisnd/msg

Made for: Claude Code.

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

PostToolUse 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.

.claude/settings.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "python3 -c \"\nimport sys, json\nd = json.load(sys.stdin)\ncmd = d.get('tool_input', {}).get('command', '')\nif any(x in cmd for x in ['git add', 'git stage']):\n    print('Changes staged — invoke /commit-this to generate a commit message.')\n\" 2>/dev/null || true"
        }
      ]
    }
  ]
}

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.

yesterday First seen · 13 lines scan A 3aefb5ec35f7

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository ndisisnd/msg (6 stars, last pushed 15d 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-31.

Git and workflow agent-skills agentic-ai agentic-coding agentic-workflows agents claude-code

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

FileChanged

UserPromptSubmit

SessionEnd

PermissionRequest

UserPromptSubmit

PostToolUse