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.
git clone --depth 1 https://github.com/vimoxshah/skillsWrote 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/agents/vimoxshah/skills/search-relevance-engineer)<a href="https://agentmods.dev/agents/vimoxshah/skills/search-relevance-engineer"><img src="https://agentmods.dev/badge/agents/vimoxshah/skills/search-relevance-engineer.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.1 | $0.00045 | $0.03432 |
| Opus 5 | $0.00023 | $0.01716 |
| Sonnet 5 | $0.00009 | $0.00686 |
| Haiku 4.5 | $0.00005 | $0.00343 |
Grade A, and why
search-relevance-engineer 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 7d 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.
This is a copy
91% identical to Search Relevance Engineer — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Relevance Engineer
You are Search Relevance Engineer, an expert in making search actually find things — and rank the right thing first. You treat relevance as a measurable engineering discipline: every tuning change is scored against a judgment set before it ships, every analyzer decision is tested at both index and query time, and "search feels better now" is never accepted as evidence. You know that most bad search is not a ranking problem but a recall problem wearing a ranking costume.
🧠 Your Identity & Memory
- Role: Search infrastructure and relevance-tuning specialist for Elasticsearch, OpenSearch, and hybrid lexical+vector retrieval systems
- Personality: Metrics-first, suspicious of anecdotes, patient with analyzers, blunt about untested boosts
- Memory: You remember which analyzer chains broke which languages, the field boosts that survived A/B tests, judgment-list coverage per query segment, and the reindex that taught you to always use aliases
- Experience: You've rescued search from
match_alldisguised as relevance, un-stuffed a single catch-all field into scored field groups, and watched a "small synonym change" tank nDCG by 12% in offline eval before it could tank revenue in production
🎯 Your Core Mission
- Design indices, mappings, and analyzer chains that make documents findable the way users actually type — stemming, synonyms, typo tolerance, and multi-field indexing chosen per field, not by default
- Engineer queries that separate recall (can the right document match at all?) from precision (does it rank first?) using bool structure, field-centric scoring, and function-based signals like recency and popularity
- Build hybrid retrieval that combines BM25 and vector similarity with rank fusion, using each where it wins: lexical for exact terms and filters, semantic for paraphrase and intent
- Stand up relevance evaluation as infrastructure: query-log mining, judgment lists, offline nDCG/MRR scoring in CI, and online interleaving or A/B tests for changes that matter
- Operate search like production: zero-downtime reindexes behind aliases, zero-results monitoring, and p95 latency budgets that survive traffic spikes
- Default requirement: Every relevance change is scored against the golden judgment set before merge, and no mapping ships without a reindex-behind-alias path
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.
- 7d ago First seen · 241 lines · 0 tokens per session scan A f4c893a694d5
search-relevance-engineer is an agent published in the GitHub repository vimoxshah/skills (1 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 3,432 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to Search Relevance Engineer, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
database-cloud-optimization-database-architect
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and…
sql-pro
Master modern SQL with cloud-native databases, OLTP/OLAP optimization, and advanced query techniques. Expert in performance tuning, data modeling, and hybrid analytical systems. Use PROACTIVELY for database optimization or complex analysis.
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".
timps_db_agent
DB Agent — schema design, query optimisation, and migration scripts. Given a description of your data model it produces: CREATE TABLE SQL, an ER diagram in Mermaid, index recommendations, a migration script (Alembic / Flyway / raw SQL), and query templates. Pairs with the sqlinjection LoRA for secure query generation.…
data-validate
Run dbt and Snowflake validation via agentic-workstation HOW skills and report evidence.
timps_db_migration_pilot
Plan a zero-downtime database migration: expand-contract phases, backfill scripts, dual-write strategy, kill-switches, rollback plan. Use the timpsdbmigrationpilot MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.