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 pushgit 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/push)<a href="https://agentmods.dev/skills/ballred/obsidian-claude-pkm/push"><img src="https://agentmods.dev/badge/skills/ballred/obsidian-claude-pkm/push/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/push"><img src="https://agentmods.dev/badge/skills/ballred/obsidian-claude-pkm/push.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.00040 | $0.00736 |
| Opus 5 | $0.00020 | $0.00368 |
| Sonnet 5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
push 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Push Skill
Automates Git workflow to save your notes with meaningful commit messages and push to remote repository.
Usage
Invoke with /push or ask Claude to save/commit your changes.
Basic Usage
/push
With Custom Message
/push "Completed project planning"
What This Skill Does
-
Stages All Changes
- Adds all modified files
- Includes new files
- Removes deleted files
-
Creates Smart Commit Message
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
-
Syncs with Remote
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
Commit Message Format
Automatic Messages
Based on your changes:
Daily note for 2024-01-15 + 3 project updates
- Added: Daily Notes/2024-01-15.md
- Modified: Projects/Learning Spanish/notes.md
- Modified: Goals/2. Monthly Goals.md
With Timestamp
[2024-01-15 09:30] Completed weekly review
Workflow Integration
Morning Routine
/daily # Create daily note
# ... work on notes ...
/push "Morning planning complete"
End of Day
# Complete daily reflection
/push # Auto-message with summary
After Weekly Review
/weekly # Run weekly review
/push "Weekly review - Week 3"
Git Operations
Standard Flow
git add .- Stage all changesgit commit -m "message"- Create commitgit pull --rebase origin main- Get remote changesgit push origin main- Push to remote
Safety Checks
- Verify Git repository exists
- Check for uncommitted changes
- Ensure remote is configured
- Validate branch exists
Conflict Handling
If conflicts occur:
- Auto-resolve attempts (favor local for notes)
- If manual resolution needed, guide through process
- Never force push without explicit request
Security Considerations
Never Commit
- Passwords or credentials
- API keys
- Personal identification
- Financial information
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 · 148 lines · 40 tokens per session scan A f3f94725d7a5
push is a skill published in the GitHub repository ballred/obsidian-claude-pkm (1,856 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 736 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
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
persona-commit
A skill for writing concise Git commit messages in Conventional Commits format, a shared style that labels changes such as features, fixes, tests, or documentation.
git-conventional-commits
Builds a Conventional Commits commit message for the current changes in git. Analyzes the staged diff (or unstaged, if staged is empty), determines type/scope, writes the subject and, if needed, a body. Use when the user wants to "make a commit", "commit the changes", "commit this", "write a commit message", "commit…
git-pr-description
Builds a Pull Request description from the diff of the current branch against the base branch (main/master). Analyzes all commits, extracts "why / what / how to verify", captures breaking changes. Use when the user wants to "describe the PR", "write a description for the pull request", "put together a PR", "push and…
develop-small-feature
Implement a small, well-scoped feature or fix end-to-end from spec to PR — reuse or create a feature branch, implement test-first, run static checks, get user verification, commit, then open a PR to main.
commit-changes
Commit the current changes with a Conventional Commits message. Use when the user asks to commit, or when a workflow (e.g. develop-small-feature) reaches its commit step after implementation is verified.