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 estuary/agent-skills --skill capture-http-ingest-creategit clone --depth 1 https://github.com/estuary/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/estuary/agent-skills/capture-http-ingest-create)<a href="https://agentmods.dev/skills/estuary/agent-skills/capture-http-ingest-create"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/capture-http-ingest-create/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/estuary/agent-skills/capture-http-ingest-create"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/capture-http-ingest-create.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.00074 | $0.01700 |
| Opus 5 | $0.00037 | $0.00850 |
| Sonnet 5 | $0.00015 | $0.00340 |
| Haiku 4.5 | $0.00007 | $0.00170 |
Grade A, and why
capture-http-ingest-create scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Test with curl How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create HTTP Ingest (Webhook) Capture
Create an Estuary capture that accepts incoming HTTP requests (webhooks) from external services.
Step 0: Load Connector Documentation
Before proceeding, fetch the official connector docs for config reference and webhook URL details:
Primary: https://docs.estuary.dev/reference/Connectors/capture-connectors/http-ingest/
Use WebFetch to load this page. The docs cover:
- Configuration reference (auth tokens, paths)
- Webhook URL format and retrieval
- Deduplication via
idFromHeader - Authentication setup
This skill provides the flowctl workflow, service-specific guidance, and troubleshooting that docs don't cover.
Step 1: Gather Requirements
Before writing any YAML, ask the user:
- What service(s) are sending webhooks? — GitHub, Shopify, Stripe, Segment, custom, etc.
- How many event types/paths? — One webhook endpoint or multiple (e.g.,
/orders,/customers) - Authentication method? — HTTP Ingest only supports Bearer token auth. If the source requires OAuth callbacks or other auth flows, stop and inform the user this connector won't work for that source.
- Non-default data plane? — Most users use the default. Ask if they need a non-default data plane (affects webhook URL domain).
Key Difference from Database Captures
HTTP Ingest works in reverse — external services push TO Estuary, rather than Estuary pulling FROM a source:
- No firewall changes needed on the user's end
- Estuary provides the public HTTPS endpoint
- Authentication is via Bearer token
- The webhook URL is only visible in the web UI after publishing — it cannot be retrieved via CLI
Step 2: Create the Capture Spec File
captures:
<tenant>/<path>/source-http-ingest:
endpoint:
connector:
image: ghcr.io/estuary/source-http-ingest:v1
config:
require_auth_token: "<secure-random-token>"
paths:
- /<path-name>
bindings: []
Generate a secure token:
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 · 210 lines · 74 tokens per session scan A 670884613749
capture-http-ingest-create is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,700 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
change-data-capture-admin
Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. NOT for writing an Apex change-event trigger — use apex/change-data-capture-apex. NOT for subscribing an external system over Pub/Sub or CometD — use…
change-data-capture-admin
Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. NOT for CDC Apex trigger implementation (use change-data-capture-integration).
stream-processing-designer
Design a stream processing system for unbounded, continuously arriving data. Use when choosing a message broker (Kafka vs RabbitMQ), implementing change data capture (CDC) from PostgreSQL, MySQL, or MongoDB via Debezium or Maxwell, selecting window types for aggregation (tumbling, hopping, sliding, session), joining…
target-connector
This skill should be used when creating a new target connector for CocoIndex to integrate with external systems. It provides guidance on implementing TargetHandler, TargetActionSink, and related types for declarative target state synchronization with change detection and automatic cleanup.
developing-kafka-java-client
Use when the user wants to integrate a Kafka client into an existing application or scaffold a Java Kafka client project (Maven or Gradle based) for Confluent Cloud, local Docker, or WarpStream. Covers the Apache Kafka Java clients (KafkaProducer/KafkaConsumer/KafkaShareConsumer) with Avro, JSON Schema, or Protobuf…
developing-kafka-python-client
Use when the user wants to build a Python Kafka producer or consumer, add Schema Registry to existing Python code, migrate from raw JSON to schema-backed serialization, or scaffold a confluent-kafka-python project for Confluent Cloud, local Docker, or WarpStream. Also use when user wants to optimize Python Kafka…