Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wrg32786/aigent-osnpx agentmods add skills/wrg32786/aigent-os/semantic-searchWrote 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/skills/wrg32786/aigent-os/semantic-search)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/semantic-search"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/semantic-search/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/skills/wrg32786/aigent-os/semantic-search"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/semantic-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00440 |
| Opus 5 | $0.00005 | $0.00220 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
semantic-search 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.
What it actually says
Vault Semantic Search
Search the Obsidian vault by meaning, not just keywords. Uses local all-MiniLM-L6-v2 model — no API calls, no data leaves your machine.
Usage
# Search by meaning
node daemons/semantic-search/search-vault.js "your query here"
# Re-index (run after significant vault changes)
node daemons/semantic-search/embed-vault.js
# Re-index only changed files
node daemons/semantic-search/embed-vault.js --changed-only
Setup
cd daemons/semantic-search && npm install
node embed-vault.js # Initial index (~30 seconds)
Confidential-class deny list
If your vault also holds client work, deal notes, or anything under NDA, keep it out of the index:
cd daemons/semantic-search
cp index-deny.example.json index-deny.json
# then edit index-deny.json and list your own folders
Each entry in deny_prefixes is a vault-relative path prefix, matched case-insensitively and with either slash style. embed-vault.js drops matching files before they are embedded, so their text never reaches embeddings.json (which stores note excerpts in plaintext). search-vault.js re-checks the same list at query time, so an index built before you added a prefix still can't return one.
Only index-deny.example.json is tracked by git. Your index-deny.json is gitignored, because the names of your confidential folders are themselves confidential. With no index-deny.json at all, both scripts index and search everything and print a notice on stderr saying so. If the file exists but can't be read or parsed, they exit non-zero instead of falling back to an unfiltered index. Add a prefix the same session confidential material enters your vault, then re-run embed-vault.js: it also purges anything already indexed under a newly added prefix.
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 · 44 lines · 11 tokens per session scan A 1b1806ebe8ef
semantic-search is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 440 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
memory-flush
Promote important recent log entries into MEMORY.md and prune stale ones.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
continuum-memory
Configure and use Continuum's two-tier memory system — mem0+Qdrant/Milvus for long-term facts, Redis for short-term sessions, with multi-tenant scopes (USER / AGENT / SHARED / RUN / CONVERSATION). Invoke when the user asks about "remember", "user preferences", "long-term memory", "vector search over memories"…
carryover
Use when recalling, saving or curating carryover memory, wikis, playbooks or the Obsidian vault.