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 uninhibited-scholar/obsidian-loop-wiki --skill skillgit clone --depth 1 https://github.com/uninhibited-scholar/obsidian-loop-wikiWrote 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/uninhibited-scholar/obsidian-loop-wiki/skill)<a href="https://agentmods.dev/skills/uninhibited-scholar/obsidian-loop-wiki/skill"><img src="https://agentmods.dev/badge/skills/uninhibited-scholar/obsidian-loop-wiki/skill/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/uninhibited-scholar/obsidian-loop-wiki/skill"><img src="https://agentmods.dev/badge/skills/uninhibited-scholar/obsidian-loop-wiki/skill.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.00208 | $0.02179 |
| Opus 5.5 | $0.00083 | $0.00872 |
| Sonnet 5.5 | $0.00042 | $0.00436 |
| Haiku 4.5 | $0.00021 | $0.00218 |
Grade A, and why
loop-wiki 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 1mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-wiki
Turn an Obsidian vault into a knowledge base that grows itself: raw material goes in, and the Agent compiles it into typed, cross-linked nodes that form a visible graph — every run leaving an audit trail you can trust.
The hard-won lesson behind this skill: an Agent left to "just organize my notes" will quietly invent a new naming scheme every day and produce AI-generated clutter instead of knowledge. The fix is Loop Engineering — treat each organizing pass as a loop with a machine-verifiable goal, guardrails on what it may not do, and a verification pass that catches the Agent gaming its own success criteria. That discipline is what makes the vault trustworthy enough to run unattended later.
Before anything: locate and validate the vault
The vault path lives in WIKI_PATH. Never guess it, never hardcode a path.
echo "$WIKI_PATH" && ls "$WIKI_PATH"
- If
WIKI_PATHis empty: ask the user for their vault path and suggest theyexport WIKI_PATH="/path/to/vault". Do not proceed without it. - If the path exists but has no
SCHEMA.md: this is an uninitialized vault. Run the Initialize a vault flow below before doing anything else. - If
SCHEMA.mdexists: readSCHEMA.md,index.md, andlog.mdfirst. These three files are the contract. The rules inSCHEMA.mdoverride your own instincts about naming and structure — follow them, don't relitigate them.
The two control files you must respect every run
| File | Role | Your obligation |
|---|---|---|
SCHEMA.md |
The rulebook: folder meanings, naming, wikilink policy | Obey it. If a rule is missing, propose adding it rather than improvising silently. |
index.md |
The entry map: links to key concepts, MOCs, recent updates | Update it whenever you add an important node. |
log.md |
The audit trail: what changed, from which source, what's unverified | Append a dated entry every run. No log entry = the change didn't happen. |
What ships with it
3 files 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.
- 1mo ago First seen · 174 lines · 208 tokens per session scan A 08e80a07480c
loop-wiki is a skill published in the GitHub repository uninhibited-scholar/obsidian-loop-wiki (2 stars, last pushed 3mo ago), licensed MIT. It adds 208 tokens to every session and 2,179 once invoked, about $0.0008 per session on Opus 5.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
notification-auto-dismiss
A notification cleaner for Stop messages from subscribed worktrees. It removes messages that are only waiting for background work to finish and leaves messages needing human input.
recap
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
turnbreak
Shows you something worth reading while your coding agent works, then notifies you when it's done. Use this skill to install turnbreak's turn-start/turn-stop hooks for Claude Code, Codex, Gemini CLI, or Copilot CLI, or to manage its interests and settings.
briefing
Create an athlete-owned calendar note.
second-brain-climb
A guide for maintaining a long-term personal direction as a structured, evidence-based plan. It describes the desired destination, current position, gaps, possible routes, limits, evidence, and next actions.
reconcile
Cross-reference a paper against the collection. Finds which cited papers are already collected, which are new leads, which collection papers cite this one, and reconciles all cross-references bidirectionally. Run on a single paper directory or use --all for the entire collection.