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.
npx agentmods add hooks/stefanwebb/named-pipes/post-tool-usegit clone --depth 1 https://github.com/stefanwebb/named-pipesWrote 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.
[](https://agentmods.dev/hooks/stefanwebb/named-pipes/post-tool-use)<a href="https://agentmods.dev/hooks/stefanwebb/named-pipes/post-tool-use"><img src="https://agentmods.dev/badge/hooks/stefanwebb/named-pipes/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>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 5d 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.
The source is not reproduced here
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What else settings.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 21 lines scan A e9317c1bc8b2
PostToolUse is a hook published in the GitHub repository stefanwebb/named-pipes (14 stars, last pushed 2mo ago), licensed CC-BY-SA-4.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-30.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup, clear and compact, executing session-brief.sh. From techtheist/engram.
Setup
Runs once when the project is set up for init and maintenance tool calls, executing setup-deps.sh with --audit-level (2 commands). From christopherlouet/claude-base.
TeammateIdle
Runs on the TeammateIdle event, running an inline shell check. From christopherlouet/claude-base.
PostCompact
Runs after the context is compacted, running an inline shell check. From christopherlouet/claude-base.
ElicitationResult
Runs on the ElicitationResult event, running an inline shell check. From christopherlouet/claude-base.
SessionStart
Runs when a session starts, running an inline shell check. From RoninForge/budgetclaw.