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.
npx skills add ballred/obsidian-claude-pkm --skill monthlygit 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/skills/ballred/obsidian-claude-pkm/monthly)<a href="https://agentmods.dev/skills/ballred/obsidian-claude-pkm/monthly"><img src="https://agentmods.dev/badge/skills/ballred/obsidian-claude-pkm/monthly/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/skills/ballred/obsidian-claude-pkm/monthly"><img src="https://agentmods.dev/badge/skills/ballred/obsidian-claude-pkm/monthly.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00032 | $0.01426 |
| Opus 5 | $0.00016 | $0.00713 |
| Sonnet 5 | $0.00006 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
monthly 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 12d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monthly Review Skill
Facilitates monthly review and planning by rolling up weekly reviews, checking quarterly milestones, and setting next month's focus.
Usage
/monthly # Run monthly review for current month
Or ask:
- "Help me with my monthly review"
- "Plan next month"
- "How did this month go?"
What This Skill Does
- Creates or opens monthly goals file (
Goals/2. Monthly Goals.md) - Rolls up weekly reviews from the past month
- Checks quarterly milestones against yearly goals
- Plans next month's focus areas and priorities
Review Process
Phase 1: Collect Monthly Data (10 minutes)
- Read all weekly reviews from the past month (
Goals/3. Weekly Review.mdor weekly review notes) - Read daily notes from past 30 days (scan for patterns)
- Read current
Goals/2. Monthly Goals.mdfor this month's targets - Scan
Projects/*/CLAUDE.mdfor project status updates
Extract:
- Wins from each week
- Challenges and recurring blockers
- Goal progress percentages
- Project milestones completed
- Habits tracked (completion rates)
Phase 2: Reflect on Month (10 minutes)
- Read
Goals/1. Yearly Goals.mdfor quarterly milestones - Calculate which quarter we're in and check milestone progress
- Identify patterns across weeks (energy, productivity, focus areas)
- Compare planned vs actual outcomes
Generate:
- Monthly accomplishment summary
- Quarterly milestone progress check
- Pattern analysis (what worked, what didn't)
- Goal alignment assessment
Phase 3: Plan Next Month (10 minutes)
- Identify next month's quarterly milestones
- Surface projects that need attention
- Set next month's primary focus (ONE thing)
- Define 3-tier priorities (must/should/nice-to-have)
- Plan habits to build or maintain
Write:
- Update
Goals/2. Monthly Goals.mdwith next month's plan - Set specific weekly milestones for the month ahead
Output Format
## Monthly Review: [Month Year]
### Month Summary
- Weeks reviewed: 4
- Daily notes analyzed: [N]
- Projects active: [N]
### Wins
1. [Major accomplishment]
2. [Progress milestone]
3. [Habit success]
### Challenges
1. [Recurring blocker]
2. [Missed target]
### Patterns
- **Energy:** [When were you most productive?]
- **Focus:** [What got the most attention?]
- **Gaps:** [What was consistently avoided?]
### Goal Progress
| Goal | Start of Month | End of Month | Delta |
|------|---------------|-------------|-------|
| [Goal 1] | 30% | 45% | +15% |
| [Goal 2] | 50% | 55% | +5% |
### Quarterly Milestone Check
**Quarter: Q[N] ([Month Range])**
| Milestone | Status | Notes |
|-----------|--------|-------|
| [Milestone 1] | On Track | [Detail] |
| [Milestone 2] | At Risk | [What's needed] |
### Project Status
| Project | Progress | Status | Next Month Focus |
|---------|----------|--------|-----------------|
| [Project 1] | 60% | Active | [Key deliverable] |
### Next Month Plan
**ONE Focus:** [Primary objective]
**Must Complete:**
1. [Non-negotiable deliverable]
2. [Critical milestone]
3. [Key commitment]
**Should Complete:**
1. [Important but flexible]
2. [Supporting goal]
**Nice to Have:**
1. [Stretch goal]
**Weekly Milestones:**
- Week 1: [Focus]
- Week 2: [Focus]
- Week 3: [Focus]
- Week 4: [Focus + monthly review]
### Wellbeing Check
- Physical Health: /10
- Mental Health: /10
- Relationships: /10
- Work Satisfaction: /10
- Overall: /10
### Questions to Consider
- "What would make next month feel truly successful?"
- "What commitment should you drop or delegate?"
- "Which goal needs a different approach?"
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.
- 12d ago First seen · 201 lines · 32 tokens per session scan A c405d1e77ac2
monthly is a skill published in the GitHub repository ballred/obsidian-claude-pkm (1,862 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,426 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 skills, from other repositories
obsidian
Organize Obsidian vaults with Markdown, URI links, Templater, Dataview, and local plugin workflows.
inbox
An inbox-management skill for scanning an LLM Wiki inbox, previewing pending files, choosing how to process them, and sending selected material through an import step.
weekly-review
Weekly patterns review - aggregate progress, insights, and alignment.
audit
Rigorous six-layer evaluation (Layers 0-5) of any implementation (code, config, plans, processes, systems) — by a cross-model panel by default, gracefully downgrading to whatever models are available, or a single model on request.
book-stay
Choose and book a hotel (or stay) — quiz preferences, generate shortlist, verify rates, hand off booking, fan out references across the vault.
landscape-scan
Topic-parameterised external-intelligence scan + digest. Default topic is the AI/Claude Code/PKM landscape; pass a topic name (e.g. cybersec) to run a different profile. Curated-source scan, user-provided URL pile, or both — assessed through the active profile's lens.