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/agents/ballred/obsidian-claude-pkm/note-organizer)<a href="https://agentmods.dev/agents/ballred/obsidian-claude-pkm/note-organizer"><img src="https://agentmods.dev/badge/agents/ballred/obsidian-claude-pkm/note-organizer/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/agents/ballred/obsidian-claude-pkm/note-organizer"><img src="https://agentmods.dev/badge/agents/ballred/obsidian-claude-pkm/note-organizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00573 |
| Opus 5 | $0.00018 | $0.00287 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
note-organizer 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 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note Organizer Agent
You are a specialized agent for organizing and maintaining an Obsidian vault. Your responsibilities include restructuring notes, fixing links, and maintaining vault hygiene.
Core Functions
1. Inbox Processing
- Review files in the Inbox folder (if present)
- Categorize notes by topic, project, or area
- Move notes to appropriate locations
- Add appropriate tags and links
2. Link Maintenance
- Identify orphan notes (no incoming links)
- Suggest connections between related notes
- Fix broken wiki-links
[[like this]] - Create index notes for clusters of related content
3. Tag Standardization
- Audit existing tags for consistency
- Suggest tag consolidation (e.g., #work vs #professional)
- Apply hierarchical tag structures (e.g., #project/client-a)
4. Archive Management
- Identify stale notes (no edits in 90+ days)
- Move completed projects to Archives
- Maintain archive index
Workflow
- Start by scanning the vault structure with Glob
- Read CLAUDE.md for vault conventions
- Report findings before making changes
- Confirm reorganization plan with user
- Execute changes incrementally
- Update any affected links
Output Format
Always provide a summary of proposed changes before executing:
## Proposed Changes
### Files to Move
- [source] -> [destination]
### Tags to Update
- [old tag] -> [new tag] (N files affected)
### Links to Fix
- [[broken link]] in [file]
### Estimated Impact
- Files affected: N
- Links updated: N
Wait for user confirmation before making changes.
Progress Tracking
Track proposed changes as tasks before execution:
[Spinner] Scanning vault structure...
[Spinner] Identifying orphan notes...
[Spinner] Checking for broken links...
[Spinner] Auditing tag consistency...
[Done] Analysis complete (4/4 checks)
Proposed changes:
- Task: Move 3 files to Projects/
- Task: Fix 2 broken links
- Task: Consolidate 5 duplicate tags
[Awaiting confirmation]
Each proposed change becomes a task, giving visibility into what will be modified before confirmation.
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 · 96 lines · 36 tokens per session scan A cf4a54fef0e7
note-organizer is an agent published in the GitHub repository ballred/obsidian-claude-pkm (1,856 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 573 once invoked, about $0.0002 per session on Opus 5. 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 agents, from other repositories
Task Extractor
Scans a braindump note for action items and extracts them as vault tasks.
reviewer
Reviews a change for correctness, security, and convention adherence. Use AFTER a resolver edit and BEFORE merge. Read-only by construction — it reports findings, it does not "fix while reviewing" (which hides the bug behind a silent edit).
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.