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/cookiemonsterdev/agents-skills/opensearch-docsnpx skills add cookieMonsterDev/agents-skills --skill opensearch-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-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/cookiemonsterdev/agents-skills/opensearch-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/opensearch-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/opensearch-docs.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.00095 | $0.01249 |
| Opus 5 | $0.00048 | $0.00624 |
| Sonnet 5 | $0.00019 | $0.00250 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
opensearch-docs 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSearch questions are easy to answer from stale Elasticsearch memory or wrong plugin names. Use this skill to ground answers in the official OpenSearch documentation and return the closest authoritative page instead of generic search-engine advice.
When to Use
Use this skill when the request is about:
- OpenSearch concepts, indices, documents, mappings, and aliases
- Getting started with OpenSearch and OpenSearch Dashboards
- Installation, configuration, upgrades, and plugins
- Indexing, updating, searching, aggregating, and deleting data
- Query DSL, SQL plugin, PPL, and search patterns
- Mappings, analyzers, index templates, and index management
- Vector search, k-NN, semantic search, and hybrid search
- ML Commons: model deployment, connectors, and AI agents
- Security plugin: authentication, authorization, and encryption
- Index State Management (ISM), snapshots, and cluster administration
- OpenSearch Dashboards: visualizations, Discover, and alerting
- Data Prepper, clients, Benchmark, and Migration Assistant
- Observability, anomaly detection, and trace analytics
- Troubleshooting cluster health, shard allocation, and query performance
Do not use this skill for:
- Elastic-licensed Elasticsearch or Kibana features documented only on
elastic.co. Useelasticsearch-docsinstead. - Amazon OpenSearch Service console operations when the question is provider-specific rather than OpenSearch behavior.
- Solr, Meilisearch, or other search engines unless the question maps to documented OpenSearch API behavior.
- MySQL or PostgreSQL relational database questions.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started and tutorials
- Install, configure, and upgrade
- Data modeling: mappings, templates, and index management
- Search, Query DSL, SQL, and PPL
- Vector search and machine learning
- Security and access control
- Cluster operations, ISM, and snapshots
- OpenSearch Dashboards and visualization
- Clients, Data Prepper, and supporting tools
- API reference and plugin docs
- Troubleshooting and migration
What ships with it
2 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.
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 · 114 lines · 95 tokens per session scan A b76532728f65
opensearch-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 16d ago), licensed MIT. It adds 95 tokens to every session and 1,249 once invoked, about $0.0005 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
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
bigquery-bigframes
Generates Python code using BigQuery DataFrames (BigFrames), the pandas/scikit-learn-style API over BigQuery. Use when writing BigFrames code or doing pandas-style dataframe/ML work against BigQuery (e.g. in a notebook). Don't use for SQL-first workflows or the google-cloud-bigquery client library — use…
cloud-databases-onboarding
Guides users through discovering their database requirements, recommends a Google Cloud database based on a recommendation matrix, and assists in database creation. Use when a user asks 'What database service should I use?', 'Help me pick a database', or when a user wants to create a new database on Google Cloud.…
spanner-basics
Assists in provisioning instances and databases, designing performant schemas, and querying data in Spanner. Use when designing primary keys, writing SQL queries or client library code, or diagnosing performance issues.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…