Azure SDK for Go is a collection of Go modules for using and managing Microsoft Azure services through code. Go developers use client modules to work with existing Azure resources and management modules to configure those resources. Its catalogue add-ons provide instructions and agent support for developing within the SDK repository.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-go/main/.github/hooks/hooks.jsongit clone --depth 1 https://github.com/Azure/azure-sdk-for-goWrote 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/azure/azure-sdk-for-go/post-tool-use)<a href="https://agentmods.dev/hooks/azure/azure-sdk-for-go/post-tool-use"><img src="https://agentmods.dev/badge/hooks/azure/azure-sdk-for-go/post-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/azure/azure-sdk-for-go/post-tool-use"><img src="https://agentmods.dev/badge/hooks/azure/azure-sdk-for-go/post-tool-use.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
This is a copy
100% identical to PostToolUse — 0 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.
What it actually says
{
"PostToolUse": [
{
"type": "command",
"command": "pwsh eng/common/scripts/azsdk_tool_telemetry.ps1",
"timeoutSec": 5
}
]
}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.
- 1mo ago First seen · 9 lines scan A 4d5c209609e8
PostToolUse is a hook published in the GitHub repository Azure/azure-sdk-for-go (1,857 stars, last pushed today), 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 100% identical to PostToolUse, differing in 0 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.
PostToolUse
Runs after a tool call finishes for Bash tool calls, executing hooks.sh via sh (3 commands). From anthropics/claude-plugins-official.
PreCompact
Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.