agentmods.dev

vault-lint

vault-lint is a skill for Claude Code from thoreinstein/obsidian-rag. It costs 65 tokens per session (939 once invoked), scanned A, a copy of vault-lint, MIT.

A health checker for an Obsidian knowledge vault. It reviews notes for required metadata, stale information, source-confidence problems, and gaps in maps of content (MOCs), which are index notes linking related notes.

In plain words
What is it for?
Use it to audit engineering notes for frontmatter fields, uncertain provenance, stale content, and missing MOC coverage, then review suggested fixes.
Why use it?
It helps find notes that do not follow the vault’s conventions or may need source checking. This makes problems in a growing collection of technical notes easier to locate and prioritize.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the obsidian-rag plugin — 13 skills, 2 agents shipped together

not rated 2repo 1mo ago A scan 65 tokens copy · 100% MIT

Good fit Use it to audit engineering notes for frontmatter fields, uncertain provenance, stale content, and missing MOC coverage, then review suggested fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thoreinstein/obsidian-rag/vault-lint
View source ↗ thoreinstein/obsidian-rag
Install

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.

Any agent
npx skills add thoreinstein/obsidian-rag --skill vault-lint
Clone the repo
git clone --depth 1 https://github.com/thoreinstein/obsidian-rag

Made for: Claude Code.

Or install obsidian-rag, the plugin that ships this one along with the rest of its 13 skills, 2 agents.

Wrote 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.

agentmods badge for vault-lint

README.md
[![agentmods](https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/vault-lint.svg)](https://agentmods.dev/skills/thoreinstein/obsidian-rag/vault-lint)
Your own site
<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/vault-lint"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/vault-lint.svg" alt="Measured on agentmods" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 939 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00939
Opus 5 $0.00032 $0.00469
Sonnet 5 $0.00013 $0.00188
Haiku 4.5 $0.00006 $0.00094

Measured 8d ago against content hash f29e242bd85a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

vault-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 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.

Origin

This is a copy

100% identical to vault-lint — 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.

skills/vault-lint/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vault Lint

Comprehensive vault health audit. Checks five dimensions and presents a prioritized report with fix options.

Checks

1. Frontmatter Compliance

Scan Engineering/ notes for missing required frontmatter fields per VAULT_CONVENTIONS:

  1. Call obsidian_list_notes with subfolder: "Engineering".
  2. For each note, call obsidian_read_note and check frontmatter for:
    • type: — must be pattern, trap, decision, or concept
    • project: — must be present
    • status: — must be present
    • tags: — must be a list
    • created: — must be a date
  3. Report notes with missing or malformed fields.
  4. Offer to fix with obsidian_update_frontmatter (one at a time, user confirms).

2. Provenance Drift

Find Engineering/ notes where the provenance: block suggests high uncertainty:

  1. From the notes already read in Check 1, filter those with provenance: frontmatter.
  2. Flag notes where inferred > 0.5 — these are majority-synthesized and may need source verification.
  3. Flag notes where ambiguous > 0.1 — these have unresolved contradictions.
  4. Report flagged notes with their provenance fractions.

3. Stale Content

If .manifest.json exists at vault root:

  1. Read it with the Read tool.
  2. For each entry in sources, check if pages_created or pages_updated notes still exist using obsidian_read_note.
  3. If a source file's modification time on disk is newer than ingested_at, the derived notes may be stale.
  4. Report stale notes and suggest re-ingesting with /wiki-ingest --force <source>.

If no .manifest.json exists, skip this check and note that no ingest tracking is available.

4. MOC Coverage

Check whether recent Engineering/ notes appear in at least one thematic MOC:

  1. Call obsidian_list_notes with subfolder: "MOCs".
  2. For each MOC, call obsidian_read_note and extract all [[wikilinks]].
  3. Build a set of all notes referenced by at least one MOC.
  4. Compare against the Engineering/ note list — any note not in the MOC set is uncovered.
  5. Exclude notes created in the last 24 hours (grace period).
  6. Report uncovered notes and suggest which MOC(s) they belong in via obsidian_rag_query (query the note title against MOC titles).

Read the full file on GitHub · 103 lines

Changes

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.

  1. 8d ago First seen · 103 lines · 65 tokens per session scan A f29e242bd85a

Subscribe to this mod's changes

vault-lint is a skill published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 939 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 vault-lint, differing in 0 lines, and is treated as a copy.

Claude CodeMemory and contextclaude-aiclaude-code-pluginclaude-skillsobsidianobsidian-md
Related

Other skills, from other repositories

acm-handoff

Use when resuming work from a previous session that reached context threshold, or when a handoff summary exists. Reads handoff state and markdown to restore context, todos, and continue seamlessly.

povvo/claudikins-automatic-context-manager · 43 tokens

acm-config

Use when the user wants to customize Claudikins Automatic Context Manager behavior, configure trigger threshold, snooze duration, summary length, or runs '/acm:config'. Interactively asks questions and saves preferences to config file.

povvo/claudikins-automatic-context-manager · 50 tokens

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…

shwetank/bettersense · 131 tokens

career-retro

Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. Trigger phrases include "run my career retro", "where am I in my career", "annual…

shwetank/bettersense · 166 tokens

doctor

Use to health-check the user's bettersense memory directory — validate the file layout, catch problems before they cost data, and set up backups. Trigger phrases include "run bettersense doctor", "check my reflection files", "is my bettersense data okay", "something seems off with my stakeholder files", "back up my…

shwetank/bettersense · 0 tokens

capture

Use to log something from the current conversation into the user's bettersense memory without re-typing it — a decision that just got made, a win that surfaced mid-discussion, an observation about a stakeholder, a self-insight. Trigger phrases include "log this", "capture this", "save that decision", "add that to my…

shwetank/bettersense · 0 tokens