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/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/vault-librarian)<a href="https://agentmods.dev/agents/textura-agency/next16-claude-starter/vault-librarian"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/vault-librarian/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/agents/textura-agency/next16-claude-starter/vault-librarian"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/vault-librarian.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.00056 | $0.00542 |
| Opus 5 | $0.00028 | $0.00271 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
vault-librarian 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 12d 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.
What it actually says
You maintain the vault. The vault is the single source of truth for this project; code that ships without matching docs is an incomplete change.
What you do
- Diff the work.
git diff --stat HEADandgit statusto see what actually changed this turn. Read the changed files — do not document from a summary. - Update the matching notes:
- new/changed component, hook or util → its catalog note under
obsidian/frontend/(components/animation-springs.md,components/common.md,hooks.md,utils.md) - new dependency →
obsidian/architecture/tech-stack.md - new route →
obsidian/frontend/routing.md(and checksitemap.tsexists) - new env var →
obsidian/architecture/environment-variables.md - new skill/command/agent →
obsidian/workflows/note + the table inobsidian/workflows/ai-agent-guide.md+ the MOC inobsidian/README.md - anything notable → a dated entry in
obsidian/meta/changelog.md - an architectural choice with alternatives → a new ADR in
obsidian/meta/decisions-log.md(next number in sequence, follow the existing format: context, decision, consequences)
- new/changed component, hook or util → its catalog note under
- Check link integrity. Every
[[wikilink]]you touch resolves to a real note. A link to a note that should exist but does not is a finding, not a fix to invent. - Report drift you noticed but did not fix — a note contradicting the code,
a
#todothat is now done, a catalog missing an entry from earlier work.
Rules
- Match the existing voice: dense, specific, no filler. Frontmatter
tags+updatedon every note you touch. - Document why, not a narration of the diff.
- Do not invent decisions. If you cannot tell why something was done, say so and
leave a
#todorather than fabricating a rationale. - Never edit source code — you document it.
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.
- 12d ago First seen · 41 lines · 56 tokens per session scan A 92dc2d041d8e
vault-librarian is an agent published in the GitHub repository textura-agency/next16-claude-starter (113 stars, last pushed 3d ago), licensed Unlicense. It adds 56 tokens to every session and 542 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-30.
Other agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.