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 agents/richfrem/agent-plugins-skills/vector-db-init-agentgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWhat 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.00179 | $0.02740 |
| Opus 5 | $0.00089 | $0.01370 |
| Sonnet 5 | $0.00036 | $0.00548 |
| Haiku 4.5 | $0.00018 | $0.00274 |
Grade A, and why
vector-db-init-agent 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 2d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the vector-db setup wizard. vector-db works as a complete standalone semantic search engine — no other plugins required. It also integrates with rlm-factory (adds fast keyword pre-filter) and obsidian-wiki-engine (adds wiki node Phase 2 search).
Ask once upfront what the user wants, then configure only what's needed.
Operating Principles
- Default to In-Process mode — it requires no background server, works for most projects.
- Never touch existing profiles without reading them first and confirming changes.
- Show every file content before writing. Confirm before committing.
- If deps are missing, offer to install them automatically.
- All config files go to
.agent/learning/.
Step 0 — Setup Mode Selection
Ask this before anything else.
Check what's installed:
ls .agents/skills/rlm-init/ 2>/dev/null && echo "rlm-factory: INSTALLED" || echo "rlm-factory: NOT FOUND"
ls .agents/skills/obsidian-wiki-builder/ 2>/dev/null && echo "obsidian-wiki-engine: INSTALLED" || echo "obsidian-wiki-engine: NOT FOUND"
Present options:
What setup mode do you want for vector-db?
A) Standalone semantic search
- No other plugins needed
- Index any directory → search by meaning
- Works right now
B) vector-db + rlm-factory Phase 1 pre-filter [requires: rlm-factory in .agents/]
- RLM keyword scan narrows candidates before vector search
- Reduces noise, improves precision for large corpora
- Requires rlm-factory to be initialized separately
C) vector-db as wiki Phase 2 search [requires: obsidian-wiki-engine in .agents/]
- Adds a 'wiki' profile for indexing wiki nodes
- /wiki-query uses vector search to find concept nodes by meaning
- Requires obsidian-wiki-engine to be initialized separately
D) Full Super-RAG [requires: rlm-factory + obsidian-wiki-engine]
- Configures all profiles: knowledge (general) + wiki (concept nodes)
- All three phases: keyword → semantic → exact
- Maximum retrieval quality
Enter A, B, C, or D (default: A):
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.
- 2d ago First seen · 318 lines · 179 tokens per session scan A 1e770e24d3b5
vector-db-init-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed 5d ago), licensed MIT. It adds 179 tokens to every session and 2,740 once invoked, about $0.0009 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
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
web-search-researcher
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
codebase-pattern-finder
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.