PostToolUse

PostToolUse is a hook for coding agents from livewithlively/lively. Its token cost is not measured, scanned A, original, AGPL-3.0.

A post-tool hook that runs after selected editing, notebook, or Lively tool calls finish.

In plain words
What is it for?
Use it to run the repository's work-flag and custom scripts after supported tool calls.
Why use it?
It automates follow-up work that would otherwise need to be remembered and run manually.

Hook

Part of the lively plugin — 1 skill, 10 hooks, 1 MCP server shipped together

One of 10 entries in hooks.json — they are configured in one file and arrive 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/livewithlively/lively/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/livewithlively/lively

Or install lively, the plugin that ships this one along with the rest of its 1 skill, 10 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/livewithlively/lively/post-tool-use.svg)](https://agentmods.dev/hooks/livewithlively/lively/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/livewithlively/lively/post-tool-use"><img src="https://agentmods.dev/badge/hooks/livewithlively/lively/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>
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 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.

plugins/lively/hooks/hooks.json · 33 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

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. 3d ago First seen · 33 lines scan A c0c0b25295c0

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository livewithlively/lively (5 stars, last pushed today), licensed AGPL-3.0. 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.