obsidian-mcp: Command for Claude Code

.claude/commands/commit.md

commit is a command for Claude Code from eddmann/obsidian-mcp. It costs 9 tokens per session (187 once invoked), scanned A, a copy of commit, MIT.

A command procedure for reviewing the current Git changes and creating a concise commit message. Git is a version-control system that records project changes over time.

In plain words
What is it for?
Use it to inspect the branch, working tree, diff, and recent history, then create a conventional Git commit for the current changes.
Why use it?
It reduces the effort of understanding staged and unstaged edits and makes the resulting commit describe the change clearly.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is eddmann/obsidian-mcp's own configuration. It tells Claude Code how to work on obsidian-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to eddmann/obsidian-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/eddmann/obsidian-mcp/main/.claude/commands/commit.md
Clone the repo
git clone --depth 1 https://github.com/eddmann/obsidian-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/eddmann/obsidian-mcp/commit/github.svg)](https://agentmods.dev/commands/eddmann/obsidian-mcp/commit)
Your own site
<a href="https://agentmods.dev/commands/eddmann/obsidian-mcp/commit"><img src="https://agentmods.dev/badge/commands/eddmann/obsidian-mcp/commit/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.

agentmods 80×15 button for commit

Your own site · 80×15
<a href="https://agentmods.dev/commands/eddmann/obsidian-mcp/commit"><img src="https://agentmods.dev/badge/commands/eddmann/obsidian-mcp/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00187
Opus 5.5 $0.00004 $0.00075
Sonnet 5.5 $0.00002 $0.00037
Haiku 4.5 $0.00001 $0.00019

Measured 2mo ago against content hash 23496b2541da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit 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 2mo 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.

Origin

This is a copy

100% identical to commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/commit.md · 20 lines

What it actually says

Context

  • Current branch: !git branch --show-current
  • Working tree status: !git status --short --branch
  • Diff (staged + unstaged): !git diff $(git rev-parse --verify HEAD 2>/dev/null || echo --cached)
  • Recent history (if available): !git log --oneline -10 || echo "No commits yet"

Your task

Analyze the context above and:

  1. Summarize the intent of the changes.
  2. Create a concise, conventional commit message (use Conventional Commits style if possible).
  3. Commit the changes git commit -m "<generated message>".
Changes

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.

  1. 2mo ago First seen · 20 lines · 9 tokens per session scan A 23496b2541da

Subscribe to this mod's changes

commit is a command published in the GitHub repository eddmann/obsidian-mcp (15 stars, last pushed 11mo ago), licensed MIT. It adds 9 tokens to every session and 187 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit, differing in 0 lines, and is treated as a copy.