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 skills add pantheon-org/tekhne --skill vault-searchgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/vault-search)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/vault-search"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/vault-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/pantheon-org/tekhne/vault-search"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/vault-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.00084 | $0.00844 |
| Opus 5 | $0.00042 | $0.00422 |
| Sonnet 5 | $0.00017 | $0.00169 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
vault-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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vault-search
Retrieve relevant memories from the vault using hybrid BM25 + vector search.
Mindset
Search before you implement, design, or debug — not after. A 2-second search that surfaces a prior constraint saves hours of work in the wrong direction. When search returns empty, say so honestly; never fabricate a memory.
When to use
- Before starting a non-trivial task: search for related prior decisions
- When the user asks "do you remember…" or "what did we decide about…"
- Before proposing an approach: check for existing constraints or patterns
- When a bug appears familiar: search for past workarounds
How to use
vault-cli search "<query>" [--top-k <n>] [--project <id>]
Exits 1 with "No results." if nothing is found.
Query construction
- Use noun phrases, not questions:
"auth token expiry"not"how does auth token expiry work?" - Use
--projectto narrow scope when working in a known project context - If the first query returns nothing, broaden: remove specific version numbers or
error codes and retry with a higher-level term (e.g.
"postgres connection"instead of"ECONNREFUSED 5432")
Handling no results
If the search exits with "No results.":
- Retry with a broader synonym query
- If still empty, tell the user no prior memory exists on this topic
- Never invent or guess at a prior decision — proceed fresh and offer to capture the new decision
Examples
vault-cli search "authentication approach"
vault-cli search "database migration strategy" --project my-app
vault-cli search "recurring TypeScript error" --top-k 3
vault-cli search "postgres connection refused" --project api
Output format
Each result shows:
1. [category] summary (date)
tier: episodic | strength: 0.87 | score: 0.0312
content preview...
Never
- Never skip search before a non-trivial implementation task — prior constraints may invalidate your approach before you write a line
- Never fabricate a memory when search returns empty — report "No results found" and proceed without invented context
- Never search with a full sentence or question — BM25 scores individual terms; verbose queries dilute signal
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/instructions.json 2.7 KB
- evals/scenario-1/capability.txt 25 B
- evals/scenario-1/criteria.json 1.0 KB
- evals/scenario-1/task.md 234 B
- evals/scenario-2/capability.txt 15 B
- evals/scenario-2/criteria.json 1016 B
- evals/scenario-2/task.md 235 B
- evals/scenario-3/capability.txt 14 B
- evals/scenario-3/criteria.json 875 B
- evals/scenario-3/task.md 217 B
- evals/scenario-4/capability.txt 19 B
- evals/scenario-4/criteria.json 1.0 KB
- evals/scenario-4/task.md 306 B
- evals/scenario-5/capability.txt 21 B
- evals/scenario-5/criteria.json 1.0 KB
- evals/scenario-5/task.md 221 B
- evals/summary_infeasible.json 58 B
- evals/summary.json 246 B
- references/query-tips.md 383 B
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.
- 10d ago First seen · 101 lines · 84 tokens per session scan A 2330b0a3dcda
vault-search is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 844 once invoked, about $0.0004 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 skills, from other repositories
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
comet-memory
A review step for deciding whether information should become durable personal memory. It can keep, update, forget, or skip memory candidates based on bounded evidence.
recall-memory
Recall relevant long-term memories on demand. Given a topic or question, judges relevance from pre-loaded metadata, loads only relevant files, and returns a concise summary to the main agent.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…
catchup
Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean. Use when the human returns after a gap, says they can't follow the project anymore, asks what happened or what a term means, or before deciding what to do next when their mental model…