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 opensearch-project/opensearch-agent-skills --skill managed-ingestion-servicegit clone --depth 1 https://github.com/opensearch-project/opensearch-agent-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/opensearch-project/opensearch-agent-skills/managed-ingestion-service)<a href="https://agentmods.dev/skills/opensearch-project/opensearch-agent-skills/managed-ingestion-service"><img src="https://agentmods.dev/badge/skills/opensearch-project/opensearch-agent-skills/managed-ingestion-service/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/opensearch-project/opensearch-agent-skills/managed-ingestion-service"><img src="https://agentmods.dev/badge/skills/opensearch-project/opensearch-agent-skills/managed-ingestion-service.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 151 Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.Fix: Verify the destination bucket is trusted and owned by you. Never upload credentials, secrets, or workspace contents to external or unverified cloud storage.
- medium Data Exfiltration · line 156 Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.Fix: Verify the destination bucket is trusted and owned by you. Never upload credentials, secrets, or workspace contents to external or unverified cloud storage.
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.00145 | $0.03482 |
| Opus 5 | $0.00072 | $0.01741 |
| Sonnet 5 | $0.00029 | $0.00696 |
| Haiku 4.5 | $0.00015 | $0.00348 |
Grade A, and why
managed-ingestion-service 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 12d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managed Ingestion Service
Overview
Ingest documents into Amazon OpenSearch at scale via OSIS pipelines. Supports both Amazon OpenSearch Service (AOS) domains and Amazon OpenSearch Serverless (AOSS) collections.
When to Use
- User has an OpenSearch domain or AOSS collection and wants to ingest documents at scale
- User wants to move from local development to cloud ingestion
- User mentions OSIS, S3 ingestion, cloud processing, managed ingestion
Ingestion Paths
| Path | Upload to S3 | OSIS Processor | Status | Best for |
|---|---|---|---|---|
| Local processing | JSONL chunks (from local Docling) | parse_json (pass-through) |
Available now | Validated locally, deploy at scale |
| Cloud ingestion | Raw PDF/DOCX/PPTX/XLSX | document_extractor |
Private beta | Full cloud processing, no local compute |
Both paths support the same sink options — the only difference is source content and processor.
Key Constraints
- AWS credentials must be configured; check first and stop if missing
- AOS domains: must be running OpenSearch 2.19+ for ASE; public domains only (no VPC)
- AOSS collections: must be in ACTIVE state before creating the pipeline
- The IAM role (
sts_role_arn) must have S3 read + OpenSearch write permissions - When using
semantic_enrichment: it creates the index automatically — do NOT create it manually parse_jsonis the OSIS processor (parses JSONL lines);semantic_enrichmentis in the sink (applies embeddings when writing) — they are independent- Save generated YAML to
.opensearch/pipelines/<pipeline-name>.yaml
Entry Point
Step 1: Validate credentials
aws sts get-caller-identity
If this fails, stop and ask the user to configure credentials.
Step 2: Determine the deploy target
Ask: "Are you ingesting into an Amazon OpenSearch Service (AOS) domain or an OpenSearch Serverless (AOSS) collection?"
AOS domain:
- Must be running OpenSearch 2.19+ for semantic_enrichment
- Verify the domain exists and is in ACTIVE state:
aws opensearch describe-domain --domain-name <domain-name> --region <region>
What ships with it
1 file 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.
- 12d ago First seen · 426 lines · 145 tokens per session scan A 3ff189a3d3bf
managed-ingestion-service is a skill published in the GitHub repository opensearch-project/opensearch-agent-skills (52 stars, last pushed 10d ago), licensed Apache-2.0. It adds 145 tokens to every session and 3,482 once invoked, about $0.0007 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-30.
Other skills, from other repositories
google-cloud-storage-fuse
Mounts Cloud Storage buckets as a POSIX file system with Cloud Storage FUSE (gcsfuse). Use when interacting with gcsfuse: decide whether FUSE, native gs:// reads, or Filestore/Managed Lustre fits a workload, deploy tuned mounts on GKE, Compute Engine, or Cloud Run, enable and size file, stat, and list caches, tune…
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.…
cloud-sql-basics
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source…
azure-resource-manager-mysql-dotnet
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database…
azure-mgmt-mongodbatlas-dotnet
Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.
azure-resource-manager-redis-dotnet
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) …