PostToolUse

A set of checks that runs after the coding agent finishes shell commands or file edits. The checks record activity and apply quality and evidence checks to the work.

In plain words
What is it for?
Use it to monitor Bash commands and Write or Edit operations made by the agent. It is intended for project activity tracking and post-change quality checks.
Why use it?
It provides a review point after changes are made, so activity and quality signals are captured without requiring manual follow-up. It can also check whether claimed work has supporting evidence.

Hook

Part of the alfred-dev plugin — 11 skills, 22 commands, 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/686f6c61/alfred-dev/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/686f6c61/alfred-dev

Or install alfred-dev, the plugin that ships this one along with the rest of its 11 skills, 22 commands, 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 88% copy Near-identical to another mod 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 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

88% identical to SessionStart — 37 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 · 46 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "python3",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/activity-capture.py"
          ],
          "timeout": 10
        },
        {
          "type": "command",
          "command": "python3",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/quality-gate.py"
          ],
          "timeout": 10
        },
        {
          "type": "command",
          "command": "python3",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/evidence-guard.py"
          ],
          "timeout": 10
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "python3",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/activity-capture.py"
          ],
          "timeout": 10
        }
      ]
    }
  ]
}
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 · 46 lines scan A f622a045674e

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 18d 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 88% identical to SessionStart, differing in 37 lines, and is treated as a copy.