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 skills/tpierrain/kenjaku/ragnpx skills add tpierrain/kenjaku --skill raggit clone --depth 1 https://github.com/tpierrain/kenjakuWrote 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/tpierrain/kenjaku/rag)<a href="https://agentmods.dev/skills/tpierrain/kenjaku/rag"><img src="https://agentmods.dev/badge/skills/tpierrain/kenjaku/rag.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 | $0.00137 | $0.01126 |
| Opus 5 | $0.00068 | $0.00563 |
| Sonnet 5 | $0.00027 | $0.00225 |
| Haiku 4.5 | $0.00014 | $0.00113 |
Grade A, and why
rag 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rag — the front door to your index
The engine already knows all of this. This skill exists for one reason: it wears the name people reach for. An owner of a RAG-backed brain types
/ragbefore anything else, and until this skill existed the host answered "Unknown command: /rag. Did you mean /run?" — pointing at an unrelated built-in. Nothing was broken; the door had no sign on it.
Principle
Report the status, never compute it. Every number below comes from a tool the vault-rag
server already exposes. This skill routes and translates — it does not derive, estimate, or infer.
A figure that no tool returned does not get said (the repo's don't pretend rule, turned inward).
Procedure
1. "Where is my index at?" → vault_stats
Call the vault_stats tool of the vault-rag MCP server and relay what it returns. It already
carries everything the question is about:
- Documents / chunks indexed, and the breakdown by note type.
- Watcher liveness — whether the live-update watcher is running, and what it last did.
- Embedder identity — which engine vectorizes the notes (fully-local, Ollama, or an API), plus the daily quota when the provider has one (an API); a local embedder has none, and none is displayed.
- Engine + index-schema versions, and whether the index was built against the running one.
Then say it in the owner's words, briefly. The useful translation, not a gloss of every line:
- Documents = your notes. Chunks = the passages they were cut into; search works on those, so a rising chunk count on a stable document count simply means notes grew.
- The watcher running = a note saved in Obsidian is searchable within seconds, with nothing to run by hand. If it is not running, say so plainly and offer step 3.
- A stale index (embedder changed, or schema moved) = search is gated until a re-index; the engine says so itself and offers the re-index. Relay the offer, do not pre-empt 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.
- 4d ago First seen · 69 lines · 137 tokens per session scan A 8dbf992b7bde
rag is a skill published in the GitHub repository tpierrain/kenjaku (80 stars, last pushed 10d ago), licensed Apache-2.0. It adds 137 tokens to every session and 1,126 once invoked, about $0.0007 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 skills, from other repositories
sql_query
当用户提出数据查询需求（如'查数'、'查一下订单量'、'有多少用户'、'帮我跑个SQL'等），使用数据源工具发现表结构，生成并执行只读 SQL 查询。.
qdrant-clients-sdk
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
usage
Wren Engine CLI workflow guide for AI agents. Answer data questions end-to-end using the wren CLI: gather schema context, recall past queries, write SQL through the MDL semantic layer, execute, and learn from confirmed results. Use when: user asks a data question, requests a report or analysis, asks about metrics…
generate-mdl
Generate a Wren MDL project by exploring a database with available tools (SQLAlchemy, database drivers, MCP connectors, or raw SQL). Guides agents through schema discovery, type normalization, and MDL YAML generation using the wren CLI. Use when: user wants to create or set up a new MDL, onboard a new data source, or…
qdrant-hybrid-search-prefetches
Constructing prefetch queries for hybrid retrieval, including sparse/dense and multi-field setups, and choosing a sparse embedding model. Use when someone asks 'dense and sparse in one search?', 'how to combine multiple fields for retrieval?', 'payloads or sparse vectors for lexical?', 'which sparse embedding model to…
qdrant-multitenancy
Guides tenant isolation architecture in Qdrant for multi-tenant or multi-user applications. Use when someone asks 'how to isolate customer data', 'how to build multi-tenant search/RAG', 'how many collections should I create', 'how to partition tenants by payload', 'a customer's data legally has to stay in a certain…