iva

Layered defense against prompt injection, data exfiltration, wallet drain, and cost overruns. Three runtime components: input sanitizer (Unicode/injection), outbound gate (secret leak prevention), spend governor (cost/volume limits). Use when processing external untrusted content (emails, webhooks, forwarded messages, web fetches, group chats), scanning outbound messages for leaked secrets, or monitoring LLM spend. Do NOT use for general security audits or penetration testing.

Schema-as-code enforcement for any Obsidian vault. Zero hardcoded domains. Use when creating vault cards, checking vault health, running schema compliance, deduplicating entities, generating MOC indexes, running decay cycles, bootstrapping a vault, fixing wikilinks, finding orphans or backlinks, extracting entities from daily files, or touching/promoting cards. Do NOT use for content generation or non-vault file operations. For quick health checks without schema enforcement, prefer vault-health skill.

Iva's daily-memory processor. Reads the day's two-sided transcript (vault/daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic — runs on any LLM driving the vault (Iva uses DeepSeek). Triggered by the daily rollup (scripts/memory/rollup.ts daily).