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 roedyrustam/vibes-plug --skill search-engine-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/search-engine-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/search-engine-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/search-engine-expert.svg" alt="Measured on agentmods" 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.00056 | $0.00783 |
| Opus 5 | $0.00028 | $0.00392 |
| Sonnet 5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
search-engine-expert 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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Engine Expert (2026 Edition)
English
Orchestration & Integration
database-orm-expert: Database indexing strategies alongside search.vector-db-rag-expert: Hybrid search (semantic + full-text).performance-web-vitals: Search latency optimization.ecommerce-expert: Product search and faceted navigation.
Description
Expert guide for implementing full-text search in web applications. Covers Typesense (typo-tolerant, easy setup), Meilisearch (Rust-based, instant search), Elasticsearch/OpenSearch (enterprise-grade), faceted search, autocomplete, search-as-you-type, relevance tuning, index optimization, and geo-search.
Trigger Conditions
- Implementing search functionality beyond basic SQL LIKE queries.
- Building autocomplete or search-as-you-type features.
- Choosing a search engine for an application.
- Implementing faceted search for e-commerce product filtering.
Search Engine Selection
| Engine | Speed | Setup | Typo Tolerance | Facets | Best For |
|---|---|---|---|---|---|
| Typesense | ★★★★★ | Easy | ✅ Built-in | ✅ | Small-medium apps |
| Meilisearch | ★★★★★ | Easy | ✅ Built-in | ✅ | Developer experience |
| Elasticsearch | ★★★★ | Complex | Plugin | ✅ | Enterprise, analytics |
| Algolia | ★★★★★ | SaaS | ✅ Built-in | ✅ | Quick integration |
// Typesense — Setup and search
import Typesense from 'typesense';
const client = new Typesense.Client({
nodes: [{ host: 'localhost', port: 8108, protocol: 'http' }],
apiKey: process.env.TYPESENSE_API_KEY!,
});
// Create collection
await client.collections().create({
name: 'products',
fields: [
{ name: 'name', type: 'string' },
{ name: 'description', type: 'string' },
{ name: 'price', type: 'float', facet: true },
{ name: 'category', type: 'string', facet: true },
{ name: 'rating', type: 'float', sort: true },
],
default_sorting_field: 'rating',
});
// Search with facets
const results = await client.collections('products').documents().search({
q: 'wireless headphones',
query_by: 'name,description',
filter_by: 'price:<100 && category:=Electronics',
facet_by: 'category,price',
sort_by: 'rating:desc',
per_page: 20,
});
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.
- 5d ago First seen · 90 lines · 56 tokens per session scan A 99cb81934c8a
search-engine-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 783 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-09-03.
Other skills, from other repositories
bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when "bullmq, bull queue, redis queue, background job, job queue, delayed job, repeatable job, worker process, job scheduling, async processing, bullmq, bull, redis, queue…
firebase
Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers…
backend
World-class backend engineering - distributed systems, database architecture, API design, and the battle scars from scaling systems that handle millions of requestsUse when "backend, api, database, postgres, mysql, mongodb, redis, graphql, rest, authentication, authorization, caching, queue, background job, webhook…
event-sourcing
Store state as immutable event log instead of current values. Build auditable, event-driven systems with full history. Use when auditability, temporal queries, or event-driven processing matters.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.