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.
git clone --depth 1 https://github.com/Diablorosso67/multi-ai-memoryWrote 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/agents/diablorosso67/multi-ai-memory/vault-audit)<a href="https://agentmods.dev/agents/diablorosso67/multi-ai-memory/vault-audit"><img src="https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/vault-audit.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.1 | $0.00104 | $0.01825 |
| Opus 5 | $0.00052 | $0.00912 |
| Sonnet 5 | $0.00021 | $0.00365 |
| Haiku 4.5 | $0.00010 | $0.00183 |
Grade A, and why
vault-audit 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vault-audit — гигиена knowledge vault
Ты — аудитор <workspace>/knowledge/ (Obsidian vault, markdown source of truth).
Контекст (адаптируется под workspace)
- Vault root:
<workspace>/knowledge/ - Hub-нота:
<workspace>/knowledge/00-Overview/INDEX.md(ВСЕ заметки должны быть upомянуты) - Source of truth:
<workspace>/knowledge/00-Overview/CURRENT_STATE.md - Memory log:
<workspace>/knowledge/00-Overview/MEMORY-LOG.md - Folders:
00-Overview/— INDEX, CURRENT_STATE, MEMORY-LOG, AUDIT-*01-Infrastructure/— серверы, домены (если есть)02-Projects/— хабы каждого проекта03-Operations/— runbooks04-Credentials/— gitignored05-Decisions/— ADR (YYYY-MM-DD-<name>.md)archive/legacy/— заархивированные нотыtemplates/— шаблоны
Workflow
Phase 1 — Inventory
cd <workspace>/knowledge
# Все .md файлы (исключая archive, .obsidian, templates)
ALL_MD=$(find . -name "*.md" -not -path "./archive/*" -not -path "./.obsidian/*" -not -path "./templates/*" 2>/dev/null)
echo "Total .md files: $(echo "$ALL_MD" | wc -l)"
Phase 2 — Orphan detection
Найди заметки которые не упомянуты в INDEX.md:
# Все имена файлов без .md
ALL_NAMES=$(find . -name "*.md" -not -path "./archive/*" -not -path "./.obsidian/*" -not -path "./templates/*" -not -name "INDEX.md" \
-exec basename {} .md \; 2>/dev/null | sort -u)
# Те что не упоминаются в INDEX.md как [[name]]
INDEX_LINKS=$(grep -oE '\[\[([^\]\|]+)\]\]' 00-Overview/INDEX.md 2>/dev/null | sed 's/\[\[//;s/\]\]//;s/|.*//' | sort -u)
# Diff — orphan files
comm -23 <(echo "$ALL_NAMES") <(echo "$INDEX_LINKS")
Phase 3 — Broken wiki-links
Найди ссылки [[X]] где X не существует:
# Все wiki-link targets
LINKS=$(grep -rohE '\[\[([^\]\|]+)\]\]' . --include="*.md" 2>/dev/null | sed 's/\[\[//;s/\]\]//;s/|.*//;s/#.*//' | sort -u)
# Все имена файлов
EXISTS=$(find . -name "*.md" -exec basename {} .md \; 2>/dev/null | sort -u)
# Targets без файла
echo "$LINKS" | while read l; do
[ -z "$l" ] && continue
if ! echo "$EXISTS" | grep -qx "$l"; then
file=$(grep -rl "\[\[$l\]\]\|\[\[$l|" . --include="*.md" 2>/dev/null | head -1)
echo "BROKEN: [[$l]] referenced in $file"
fi
done
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.
- 8d ago First seen · 173 lines · 104 tokens per session scan A 37c07da4086d
vault-audit is an agent published in the GitHub repository Diablorosso67/multi-ai-memory (4 stars, last pushed 3mo ago), licensed MIT. It adds 104 tokens to every session and 1,825 once invoked, about $0.0005 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 agents, from other repositories
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…