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 li1-user/obsidian-mcp-bridge --skill obsidian-note-maintenancegit clone --depth 1 https://github.com/li1-user/obsidian-mcp-bridgeWrote 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/li1-user/obsidian-mcp-bridge/obsidian-note-maintenance)<a href="https://agentmods.dev/skills/li1-user/obsidian-mcp-bridge/obsidian-note-maintenance"><img src="https://agentmods.dev/badge/skills/li1-user/obsidian-mcp-bridge/obsidian-note-maintenance/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/li1-user/obsidian-mcp-bridge/obsidian-note-maintenance"><img src="https://agentmods.dev/badge/skills/li1-user/obsidian-mcp-bridge/obsidian-note-maintenance.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.00102 | $0.01767 |
| Opus 5 | $0.00051 | $0.00883 |
| Sonnet 5 | $0.00020 | $0.00353 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
obsidian-note-maintenance 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 10d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Note Maintenance
Safely decide whether and where focused knowledge belongs. Prefer durable integration over producing a new file for every request.
Hard boundaries
- Write only through approved Obsidian MCP tools such as
create_note,append_note,preview_patch, andapply_patchwhen available. - Never use shell, local filesystem access, another connector, or an unapproved tool to bypass MCP policy.
- Obey the server's live writable roots, protected roots, hidden-path rules, traversal checks, symlink/junction protection, exact matching, SHA-256 checks, safe writes, and audit logging.
- Never add unsupported delete, rename, move, batch overwrite, or arbitrary file-write behavior.
- Never invent approval parameters or claim that a write occurred when tools are unavailable.
- Keep work within the user's focused maintenance scope.
Do not assume a fixed Vault taxonomy or protected-directory name. Discover allowed paths from live tool behavior, user configuration, and nearby notes.
Routing
- Make this primary for a focused Vault write, even when discovery is required first.
- Route heterogeneous recent batches to
daily-knowledge-ingest. - Let
method-training-coachlead active training. - Let
method-evidence-reviewfinish explicit evidence or readiness judgments before any write handoff. - Route pure lookup to
obsidian-knowledge-retrieval. - Honor read-only instructions literally.
Preserve task-local goal, exact scope, one-task mode override, confirmed attribution, Practice Thread, factual uncertainty, note-scope decision, and preview/hash state across handoffs. Evidence approval never confirms an unseen Patch.
Tool roles
- Search before writing and read only materially relevant candidates.
- Use
list_notesonly when search terms are unavailable or structure must be inspected. - Read the persistent write mode before changing structured content.
- Change persistent mode only on explicit lasting intent.
- Create only for genuinely new durable knowledge without a suitable existing home.
- Append only to genuinely chronological or append-oriented notes.
- Preview every ordinary structured edit.
- Apply only with the exact current preview hash.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 173 lines · 102 tokens per session scan A 64487db8ae6f
obsidian-note-maintenance is a skill published in the GitHub repository li1-user/obsidian-mcp-bridge (0 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,767 once invoked, about $0.0005 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.