agentmods.dev

PostToolUse

A post-action hook that runs three Python scripts after supported coding-agent tools finish. It records identity, Git details, and MCP tool information.

In plain words
What is it for?
It is for tracking who used the agent, which Git repository was involved, and which connected MCP tools were called.
Why use it?
It keeps these records up to date automatically after tool use, so they do not have to be collected by hand.

Hook

140 4d ago A scan tokens not measured no licence
View the source file bitwarden/ai-plugins
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/bitwarden/ai-plugins/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/bitwarden/ai-plugins
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 unknown 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/bitwarden-ai-telemetry/hooks/hooks.json · 34 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 34 lines scan A 88f800de4247

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository bitwarden/ai-plugins (140 stars, last pushed 4d ago), with no licence file. 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-30.

Analytics and metricsGit and workflowPlanning
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 on startup, executing install_pkgs.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

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

SessionStart

Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From obra/superpowers.

obra/superpowers · not measured