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 Howie126313/obsidian-vault-kit --skill vault-lintgit clone --depth 1 https://github.com/Howie126313/obsidian-vault-kitWrote 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/howie126313/obsidian-vault-kit/vault-lint)<a href="https://agentmods.dev/skills/howie126313/obsidian-vault-kit/vault-lint"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/vault-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/skills/howie126313/obsidian-vault-kit/vault-lint"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/vault-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.00063 | $0.01255 |
| Opus 5 | $0.00032 | $0.00628 |
| Sonnet 5 | $0.00013 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
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 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Lint — Knowledge Base Health Check
Inspired by Karpathy's "Lint" philosophy: periodically scan the vault to surface inconsistencies, broken links, orphan pages, and data gaps.
Workflow
Step 1: Environment Detection
1a. Detect vault root — follow ../../_shared/common-steps.md "Vault Detection" section.
1b. Scan all article files:
Glob("**/*.md", path="$VAULT_ROOT")
Exclude .claude/, .git/, .playwright-mcp/, reviews/, node_modules/ directories.
Build the file list $ALL_ARTICLES.
Step 2: Six Checks
Check 1: Broken Links
Scan all articles for [[wikilink]] and [[wikilink|alias]]:
Grep("\\[\\[.*?\\]\\]", path="$VAULT_ROOT", glob="**/*.md", output_mode="content")
For each wikilink:
- Extract the link target (the part before
|) - Look for a matching file in
$ALL_ARTICLES(filename without.mdextension) - No match → record as broken link, note the source file and line number
Check 2: Orphan Pages
For each file in $ALL_ARTICLES:
- Extract the filename (without path and extension)
- Search all other articles for
[[filename]]or[[filename| - No inbound links → record as orphan page
Exclude index.md, README.md, CLAUDE.md (these naturally have no inbound links).
Check 3: index.md Consistency
- Read
$VAULT_ROOT/index.md - Compare against
$ALL_ARTICLES:- Entry in index.md but file doesn't exist → ghost entry
- File exists but no entry in index.md → missing entry
- Check whether
total_articlescount in the index.md header is accurate
Check 4: Cross-Reference Suggestions
For each article:
- Extract 3-5 core keywords (from title and tags)
- Search other articles for these keywords
- If article A frequently mentions core concepts of article B but has no
[[B]]link → suggest adding a cross-reference
This check is time-intensive; limit to 10 most recently modified articles per run.
Check 5: Summary Quality
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 · 147 lines · 63 tokens per session scan A 312f6d5c9d37
vault-lint is a skill published in the GitHub repository Howie126313/obsidian-vault-kit (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,255 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-31.
Other skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
phx-audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.