Borrowing it
Nothing to install: this file belongs to TomasHer/prompting-blueprints. 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/TomasHer/prompting-blueprints/main/.claude/settings.jsongit clone --depth 1 https://github.com/TomasHer/prompting-blueprintsWrote 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/tomasher/prompting-blueprints/post-tool-use)<a href="https://agentmods.dev/hooks/tomasher/prompting-blueprints/post-tool-use"><img src="https://agentmods.dev/badge/hooks/tomasher/prompting-blueprints/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 8d 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.
What it actually says
{
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "cmd=$(jq -r '.tool_input.command // \"\"'); case \"$cmd\" in *\"git commit\"*) python3 scripts/build-recent-additions.py >/dev/null 2>&1; if ! git diff --quiet -- README.md 2>/dev/null; then echo '{\"hookSpecificOutput\":{\"hookEventName\":\"PostToolUse\",\"additionalContext\":\"scripts/build-recent-additions.py refreshed the README Recently added list; README.md now has uncommitted changes. Stage and commit README.md so the refresh is included in this change.\"}}'; fi ;; esac",
"statusMessage": "Refreshing README Recently added list"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 2. 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.
- 8d ago First seen · 14 lines scan A 8ab4235a6584
PostToolUse is a hook published in the GitHub repository TomasHer/prompting-blueprints (22 stars, last pushed 2d 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-30.
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.
SessionStart
Runs when a session starts on startup, executing install_pkgs.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.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
PreCompact
Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.