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 thoreinstein/gemini-obsidian --skill moc-updategit clone --depth 1 https://github.com/thoreinstein/gemini-obsidianWrote 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/thoreinstein/gemini-obsidian/moc-update)<a href="https://agentmods.dev/skills/thoreinstein/gemini-obsidian/moc-update"><img src="https://agentmods.dev/badge/skills/thoreinstein/gemini-obsidian/moc-update.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.00369 |
| Opus 5 | $0.00028 | $0.00185 |
| Sonnet 5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
moc-update 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- moc-update — 100% identical, 0 lines differ
What it actually says
MOC Update After New Note
Find the Maps of Content (MOCs) that should link to a newly created note and suggest the additions.
Workflow
-
Identify the new note — Path follows the skill invocation. If not provided, ask.
-
Semantic MOC search — Call
obsidian_rag_querywith the note title as query,limit: 10. Flag results that are MOC-style notes (path contains "MOC", filename ends in "-MOC", ortype: mocfrontmatter). -
Keyword fallback — Call
obsidian_search_noteswith key terms from the note title to catch MOCs that aren't yet indexed. -
Present suggestions — For each candidate MOC, show:
- The MOC path
- Which heading the link should go under (if readable)
- A proposed link line:
- [[NoteName]] — one-line description
-
Append on confirmation — Call
obsidian_insert_at_heading(preferred) orobsidian_append_noteto add the link. Never edit without user approval.
Arguments
New note path: /moc-update Engineering/AuthPatterns.md
Tips
- If the vault has no MOCs yet, offer to create a starter one at
MOCs/<Topic>-MOC.md - Daily Notes are not MOCs — skip them in results
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.
- 8d ago First seen · 40 lines · 57 tokens per session scan A 4b7548e8746e
moc-update is a skill published in the GitHub repository thoreinstein/gemini-obsidian (102 stars, last pushed 1mo ago), licensed ISC. It adds 57 tokens to every session and 369 once invoked, about $0.0003 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
expert-librarian
An expert librarian that helps you organize, search, and synthesize your Readwise highlights and documents.
security-patcher
Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
ticket-manager
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
prd-drafter
Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work.".