agentmods.dev

PostToolUse

A post-tool hook that runs a Node.js guidance check after Bash, patch, edit, or write operations. A hook is an automatic action triggered by another tool finishing.

In plain words
What is it for?
It helps run Agentled's turn-guidance check after shell commands and file modifications.
Why use it?
It checks for Agentled feedback signals after file or command changes, so relevant guidance can be surfaced during the work.

Hook

3 11d ago A scan tokens not measured original MIT
View the source file Agentled/mcp-server
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/agentled/mcp-server/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/Agentled/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 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.

plugins/agentled/hooks/hooks.json · 15 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash|apply_patch|Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "node ${PLUGIN_ROOT}/hooks/agentled-turn-guidance.mjs --source tool",
          "statusMessage": "Checking for Agentled feedback signals",
          "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. 2d ago First seen · 15 lines scan A 961111d2001c

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository Agentled/mcp-server (3 stars, last pushed 11d 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.

Related

Other hooks, from other repositories

PostToolUse

Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.

supabase/supabase · not measured

SessionStart

Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.

google-gemini/gemini-cli · not measured

SessionStart

Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.

supabase/supabase · not measured

PreToolUse

Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.

apache/superset · not measured

PreToolUse

Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.

anthropics/claude-cookbooks · not measured

SessionStart

Runs when a session starts, executing session-start.sh. From anthropics/claude-cookbooks.

anthropics/claude-cookbooks · not measured