Post-action hooks that run after shell commands or file edits in a Nometria project. They can start deployments, create pull-request previews, check application health, and refresh a live staging preview.

Automatically syncing commits, branches, pull requests, and edits to staging, printing preview URLs, checking for HTTP 200 responses, and rolling back unhealthy deployments.

They reduce the manual work needed to keep previews current and verify deployments. Failed health checks can trigger a rollback after three unsuccessful checks.

PostToolUse — Hook by nometria

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/nometria/claude-code-plugin/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/nometria/claude-code-plugin

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 2d 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.

hooks/hooks.json · 34 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/auto-deploy-on-commit.sh",
          "description": "Triggers a resync when a git commit is made in a Nometria project."
        },
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/pr-preview.sh",
          "description": "Auto-deploys a staging preview when a PR is opened or a branch is pushed, and prints the preview URL."
        },
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/post-deploy-healthcheck.sh",
          "description": "After a deploy, verifies the app serves HTTP 200 and rolls back after 3 failed checks."
        }
      ]
    },
    {
      "matcher": "Edit|Write|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/live-preview-on-edit.sh",
          "description": "Resyncs the staging preview after code edits so there is always a live URL (debounced)."
        }
      ]
    }
  ]
}

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.

2d ago First seen · 34 lines scan A fea11baefc6d

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository nometria/claude-code-plugin (3 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-31.

DevOps and cloud Git and workflow

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

PostToolUse

SessionStart

SessionStart

PreToolUse

SessionStart

SessionStart