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 instructions/rogerdigital/vault-inspector/agents-mdgit clone --depth 1 https://github.com/rogerdigital/vault-inspectorWrote 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/instructions/rogerdigital/vault-inspector/agents-md)<a href="https://agentmods.dev/instructions/rogerdigital/vault-inspector/agents-md"><img src="https://agentmods.dev/badge/instructions/rogerdigital/vault-inspector/agents-md.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 | $0.01205 | $0.01205 |
| Opus 5 | $0.00602 | $0.00602 |
| Sonnet 5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
vault-inspector AGENTS.md 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vault-inspector CLAUDE.md — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Inspector
Obsidian plugin that scans a vault for maintenance problems. Read-only by design — no file mutation except exported reports.
- Plugin ID:
vault-inspector - Current version:
0.6.0 - Min Obsidian version:
1.7.2
Commands
npm run dev # watch mode
npm run lint # eslint
npm run lint:obsidian-warnings # Obsidian review warning checks
npm run build # tsc + esbuild production
npm test # vitest run
npm run test:watch # vitest watch
npm run test:coverage # vitest with v8 coverage
npm pack --dry-run # inspect npm package contents before publishing
Always run npm run lint && npm run lint:obsidian-warnings && npm run build && npm test before committing. CI enforces this.
Architecture
src/
main.ts Plugin entry, registers scanners/views/commands
settings/
settings.ts InspectorSettings type + defaults
settings-tab.ts Obsidian PluginSettingTab UI
scanner/
Issue.ts Issue, ScanResult, ScannerId, FixAction types
ScanContext.ts Read-only snapshot passed to scanners
ScanRunner.ts Orchestrates enabled scanners
issue-fingerprint.ts Deterministic issue IDs
scanners/ One file per scanner, pure logic
broken-links.ts Broken link detection
duplicate-files.ts Duplicate file detection
empty-notes.ts Empty note detection
external-links.ts External URL validation
frontmatter-types.ts Frontmatter type consistency
large-files.ts Large file detection
orphan-attachments.ts Unreferenced attachments
tag-usage.ts Tag usage monitoring
report/
InspectorView.ts ItemView — dashboard + interactions
ReportModel.ts View state management
render-summary.ts Summary stats
render-issues.ts Issue list with actions
markdown-export.ts Report → Markdown
fix/
confirm-modal.ts Fix confirmation modal
fix-executor.ts Executes fix actions (trash-file, remove-link-text)
utils/ Shared helpers (paths, file-types, format, hash, frontmatter-type)
tests/ Unit tests per scanner + utils
cli/ Standalone Node CLI (outside src/ so Obsidian review rules don't flag Node APIs)
bin.ts CLI process entrypoint
cli.ts CLI argument/config handling and JSON/Markdown output
local-vault.ts Local filesystem adapter for scanner reuse
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.
- 4d ago First seen · 94 lines · 1,205 tokens per session scan A 626af46a4273
vault-inspector AGENTS.md is an instructions file published in the GitHub repository rogerdigital/vault-inspector (7 stars, last pushed today), licensed MIT. It adds 1,205 tokens to every session, about $0.0060 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.