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 mickeyyaya/refactoring-skills --skill search-indexing-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-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/skills/mickeyyaya/refactoring-skills/search-indexing-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/search-indexing-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/search-indexing-patterns/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/mickeyyaya/refactoring-skills/search-indexing-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/search-indexing-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.05636 |
| Opus 5 | $0.00032 | $0.02818 |
| Sonnet 5 | $0.00013 | $0.01127 |
| Haiku 4.5 | $0.00006 | $0.00564 |
Grade A, and why
search-indexing-patterns 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 9d 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search and Indexing Patterns for Code Review
Overview
Poor mapping design causes mapping explosions, wrong query types bypass the index, unbounded aggregations exhaust heap, and deep pagination scans millions of documents. Use this guide when reviewing or designing any system that indexes or queries data — Elasticsearch, OpenSearch, or PostgreSQL full-text search.
When to use: Reviewing Elasticsearch/OpenSearch index mappings, query builders, aggregation pipelines, pagination code, bulk indexing pipelines, or PostgreSQL full-text search schemas.
Quick Reference
| Pattern | Core Idea | Primary Red Flag |
|---|---|---|
| Explicit Mapping | Define field types upfront; disable dynamic mapping | "dynamic": true on unbounded fields; mapping explosion |
| Index Lifecycle / Aliases | Aliases as stable endpoints; reindex behind the alias | Querying the real index name; no alias on write path |
| Bool Query | must/should/filter/must_not compose queries safely |
Mixing filters into must; no filter clause for exact matches |
| Boosting | boost or function_score tunes relevance |
Static score multipliers that are never revisited |
| Aggregations | terms, date_histogram, nested aggregation patterns |
Unbounded terms size; size: 0 missing on agg-only queries |
| Pagination | search_after for deep pages; PIT for stable snapshots |
from + size > 10000; scroll held open indefinitely |
| Bulk Indexing | _bulk API batches writes; tune refresh_interval |
Per-document indexing in a loop; refresh after every doc |
| PostgreSQL FTS | tsvector + GIN index + pg_trgm for fuzzy |
LIKE '%term%' instead of @@; no GIN index on tsvector column |
Patterns in Detail
1. Mapping Design — Explicit vs Dynamic
Elasticsearch and OpenSearch infer field types on first document. Uncontrolled dynamic mapping creates thousands of fields, exhausts cluster state memory, and makes schema changes impossible without reindex.
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.
- 9d ago First seen · 572 lines · 64 tokens per session scan A f7fc2cae0f32
search-indexing-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 5,636 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…