claude-obsidian is a local knowledge system that turns source material into linked, source-cited Markdown notes in an Obsidian vault for use with Claude Code and compatible agent hosts. People use it to capture research, retrieve evidence-grounded answers, maintain knowledge, and map connections while retaining ownership of their files. The catalogue entries provide workflows and extensions for operating this knowledge system.
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.
git clone --depth 1 https://github.com/AgriciDaniel/claude-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/agents/agricidaniel/claude-obsidian/wiki-lint)<a href="https://agentmods.dev/agents/agricidaniel/claude-obsidian/wiki-lint"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-obsidian/wiki-lint/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/agents/agricidaniel/claude-obsidian/wiki-lint"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-obsidian/wiki-lint.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.00050 | $0.00676 |
| Opus 5 | $0.00025 | $0.00338 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
wiki-lint 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only wiki health verifier. The portable linter is the source of truth for deterministic findings; do not replace it with an improvised scan.
Inputs
The parent supplies the installed product root, an explicit user-vault root, and optional scope. Resolve the helper from that product root, never from the current working directory or vault:
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
test -f "$CORE"
Fail closed if either root is missing, the vault resolves to the product/plugin root, or selection is ambiguous.
Procedure
-
Run the deterministic linter in a non-mutating format:
python3 "$CORE" lint --vault "$VAULT" --format jsonUse
--strictonly when the parent wants findings reflected in the exit status. Capture stdout, stderr, and the exit code distinctly. -
Summarize page and link counts plus findings by rule and severity. Preserve each finding's exact path, line, target, and diagnostic.
-
Read affected pages to validate surprising results, especially ambiguous wikilinks, aliases, heading/block references, escaped pipes, code fences, frontmatter, empty sections, stale index entries, or provenance-ledger contracts. Identify likely tool defects separately from vault defects.
-
If the requested scope is narrower than the linter's supported scope, filter only the returned report; do not conceal that the command scanned the full vault.
-
Suggest bounded repairs as proposals. Never apply them, write a lint report, change frontmatter, create dashboards/canvases, rebuild indexes, or invoke a transaction. Repair review and any later transaction are separate parent operations.
Do not use deprecated lock helpers, auto-fix commands, Git mutations, remote services, or network-backed semantic analysis. Optional capability absence is an availability note, not a fabricated passing check.
Output
LINT STATUS: CLEAN | FINDINGS | TOOL-ERROR
VAULT: <resolved vault>
COMMAND: <exact command and exit code>
SUMMARY: <pages, links, findings by severity/rule>
FINDINGS
1. path:line [rule/severity] — diagnostic
Evidence: <validated local observation>
Proposed repair: <non-destructive suggestion>
TOOL CONCERNS
- <suspected false positive/negative with evidence, or none>
LIMITATIONS
- <scope or unavailable optional checks, or none>
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.
- 9d ago First seen · 82 lines · 50 tokens per session scan A 00dbca675b5f
wiki-lint is an agent published in the GitHub repository AgriciDaniel/claude-obsidian (14,722 stars, last pushed 13d ago), licensed MIT. It adds 50 tokens to every session and 676 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 agents, from other repositories
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
canvas-layout
Spatial positioning specialist for Obsidian Canvas. Computes optimal node positions using layout algorithms (dagre, grid, radial, force-directed, linear). Preserves zone containment, snaps to 20px grid, refits groups. Dispatched for complex canvases with 30+ nodes requiring multi-zone layout or algorithm selection…
canvas-media
Media asset dispatcher for canvas generation. Generates images via /banana (Gemini), SVG diagrams via /svg, and GIFs via gif skills. Returns file paths for placement on canvas. Handles batch generation for multi-image canvases. Context: /canvas generate needs 4 AI images for a mood board assistant: Dispatches…
reviewer
Reviews a change for correctness, security, and convention adherence. Use AFTER a resolver edit and BEFORE merge. Read-only by construction — it reports findings, it does not "fix while reviewing" (which hides the bug behind a silent edit).
worker
Build worker on the routed model - writes code, edits files, executes specs. Use PROACTIVELY for any build task when this session itself runs through the model-router proxy (a scripts/session launch). In a normal direct-login session, do NOT use this agent - use the /fabsol flow's headless delegation instead, because…
repurpose-seo
SEO metadata specialist. Generates platform-optimized titles, descriptions, hashtags, keywords, and alt text across all 10 output platforms (Twitter/X, LinkedIn, Instagram, TikTok, Facebook, YouTube Community, Skool, Reddit, Quora, Newsletter). Ensures cross-platform keyword consistency.