Obsidian + Claude Code Accountability System is a personal knowledge-management setup that connects long-term goals with projects, reviews, daily notes, and tasks inside Obsidian. People use it to plan work, track progress, and review whether daily activity supports their goals with help from Claude Code. Its catalogue add-ons implement the system's planning, tracking, and review workflows.
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.
git clone --depth 1 https://github.com/ballred/obsidian-claude-pkmWrote 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/ballred/obsidian-claude-pkm/post-tool-use)<a href="https://agentmods.dev/hooks/ballred/obsidian-claude-pkm/post-tool-use"><img src="https://agentmods.dev/badge/hooks/ballred/obsidian-claude-pkm/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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- PostToolUse — 100% identical, 0 lines differ
What it actually says
{
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": ".claude/hooks/auto-commit.sh \"$TOOL_INPUT_FILE_PATH\""
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 4. 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.
- 9d ago First seen · 13 lines scan A cde5130a4e98
PostToolUse is a hook published in the GitHub repository ballred/obsidian-claude-pkm (1,856 stars, last pushed 6mo 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
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running an inline shell check. From bashiraziz/llm-wiki-template.
PreCompact
Runs before the context is compacted, executing export-session.py via python3 with --trigger. From bashiraziz/llm-wiki-template.
SessionStart
Runs when a session starts, executing index-sessions.sh via bash with --recent. From bashiraziz/llm-wiki-template.
SessionEnd
Runs when a session ends, executing export-session.py via python3 with --trigger. From bashiraziz/llm-wiki-template.
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.