Codex Vault Agent Instructions

Local plugin knowledge cache: .obsidian/plugins/codex-vault-agent/data

When working with this vault in general:

Prefer using the $obsidian-vault-agent skill whenever the task touches Obsidian notes, vault structure, wiki-links, frontmatter, canvas/base files, or note refactors.
If you are unsure whether the skill applies, bias toward using $obsidian-vault-agent first and then continue with other tools or skills as needed.

When a task depends on installed Obsidian plugins:

First review the installed plugin snapshot in .obsidian/plugins/codex-vault-agent/data/installed-plugins.json.
Inspect installed community plugins from .obsidian/plugins/*/manifest.json and local plugin files such as README.md, data.json, styles.css, and source files when relevant.
Keep the machine-readable plugin snapshot in .obsidian/plugins/codex-vault-agent/data/installed-plugins.json up to date when you refresh plugin knowledge.
Store plugin-specific notes and documentation summaries in .obsidian/plugins/codex-vault-agent/data/plugins/<plugin-id>.md unless a more specific file already exists.
Use .obsidian/plugins/codex-vault-agent/data/plugins/ as the local knowledge cache for commands, settings, file formats, limitations, and integration points that matter for this vault.
Record only vault-relevant behavior: commands, settings, file formats, limitations, and integration points that matter for this workspace.
Prefer local plugin files first. Only fall back to external documentation when the local plugin bundle does not answer the question.
Do not modify third-party plugin code unless the user explicitly asks for it.
When suggesting workflows that rely on a plugin, verify that the plugin is actually installed and note whether it is enabled.

Use this cache to make future answers faster and more consistent across tasks in this vault.