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/plugins/ballred/obsidian-claude-pkm/vault-template)<a href="https://agentmods.dev/plugins/ballred/obsidian-claude-pkm/vault-template"><img src="https://agentmods.dev/badge/plugins/ballred/obsidian-claude-pkm/vault-template/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/plugins/ballred/obsidian-claude-pkm/vault-template"><img src="https://agentmods.dev/badge/plugins/ballred/obsidian-claude-pkm/vault-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vault-template 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 body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
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
{
"name": "obsidian-pkm",
"version": "2.0.0",
"description": "Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching",
"author": {
"name": "Bill Allred",
"url": "https://github.com/ballred"
},
"repository": "https://github.com/ballred/obsidian-claude-pkm",
"license": "MIT",
"capabilities": {
"commands": true,
"agents": true,
"skills": true,
"hooks": true,
"outputStyles": true,
"rules": true
},
"keywords": [
"obsidian",
"pkm",
"productivity",
"goals",
"daily-notes",
"weekly-review",
"gtd"
]
}
What it installs
The manifest is a name and a version. 13 skills, 4 agents, 3 hooks travel with it, and installing the plugin installs all of them — 624 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill adopt A 36 tokens
- Skill daily A 41 tokens
- Skill onboard A 40 tokens
- Skill weekly A 38 tokens
- Skill goal-tracking A 41 tokens
- Skill monthly A 32 tokens
- Skill project A 35 tokens
- Skill review A 37 tokens
- Skill upgrade A 36 tokens
- Skill check-links A 32 tokens
- Skill push A 40 tokens
- Skill obsidian-vault-ops A 42 tokens
- Skill search A 31 tokens
- Agent goal-aligner A 37 tokens
- Agent inbox-processor A 34 tokens
- Agent weekly-reviewer A 36 tokens
- Agent note-organizer A 36 tokens
- Hook PostToolUse A not measured
- Hook SessionStart A not measured
- Hook UserPromptSubmit A not measured
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 · 29 lines scan A 5d566cc80834
vault-template is a plugin published in the GitHub repository ballred/obsidian-claude-pkm (1,884 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
para-knowledge-base
Build, query, index, and audit portable PARA knowledge bases in Obsidian with privacy-safe operation telemetry.
enzyme
Retired: install Enzyme with its command-line installer instead. Connects Enzyme's agent skills to a local knowledge vault.
obsidian-vfs
Resolve @obs: mentions, and /obs: Skills from your Obsidian vault into Claude.
opencairn
Skills for Claude Code: park/pickup session chaining, morning/afternoon/goodnight day loops, weekly & quarterly reviews, a six-layer cross-model audit panel, and PKM utilities. Designed to pair with the OpenCairn NIPARAS vault, but the skills install standalone.
codex-obsidian-loop
Task-driven Codex + Obsidian loop for agent memory, source boundaries, durable result writeback, and lint.
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…