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 agentmods add skills/thoreinstein/obsidian-rag/moc-updatenpx skills add thoreinstein/obsidian-rag --skill moc-updategit clone --depth 1 https://github.com/thoreinstein/obsidian-ragWrote 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/obsidian-rag/moc-update)<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/moc-update"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/moc-update.svg" alt="Measured on agentmods" 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.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 5d 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.
This is a copy
100% identical to moc-update — 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.
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.
- 5d ago First seen · 40 lines · 57 tokens per session scan A 4b7548e8746e
moc-update is a skill published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 1mo ago), licensed MIT. 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. It is 100% identical to moc-update, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
tasknotes
Manage tasks in an Obsidian TaskNotes vault. Use for creating, reading, updating, or completing tasks; checking what is open or in progress; adding items to a list; marking tasks done or in progress; updating task status or priority; investigating why a task is missing from a view or board; troubleshooting TaskNotes…
create-cmd-instruct
Reshape my PREVIOUS message using extra instructions, then save it as a slash command.
list-cmds
List all my custom slash commands with their descriptions. Use when the user wants to see, browse, or review the custom slash commands they have saved.
coaching-mode
Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation…
manage-glue-workers
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
user-profile
Use to create or update the user's anchor profile — a single private file (/bettersense-work-reflections/profile.md) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves…