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-hubspot-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-hubspot-create)<a href="https://agentmods.dev/skills/estuary/agent-skills/capture-hubspot-create"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/capture-hubspot-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-hubspot-create"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/capture-hubspot-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.00077 | $0.03827 |
| Opus 5 | $0.00039 | $0.01913 |
| Sonnet 5 | $0.00015 | $0.00765 |
| Haiku 4.5 | $0.00008 | $0.00383 |
Grade A, and why
capture-hubspot-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 10d 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.
A small local helper (HTTP server on the registered redirect URI + `curl` for the token exchange) is the most reliable way to drive the code-to-refresh-token step from a CLI workflow. `flowctl raw oauth` exists for this How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create HubSpot (Real-Time) Capture
Create a HubSpot capture using flowctl to stream CRM data from HubSpot into Estuary collections in real time.
Applies to: source-hubspot-native (HubSpot Real-Time connector)
Step 0: Load Connector Documentation
Before proceeding, fetch the official connector docs for prerequisites, config reference, and OAuth setup.
Load the docs page: https://docs.estuary.dev/reference/Connectors/capture-connectors/HubSpot-real-time/
Use WebFetch to load this page. It covers:
- Supported HubSpot resources (Contacts, Companies, Deals, Tickets, Custom Objects, etc.)
- OAuth2 authentication and scopes
- Full config property reference
- Calculated property refresh behavior
- Custom object naming (
useLegacyNamingForCustomObjects)
Search Kapa for tribal knowledge (if the Estuary MCP is configured):
Search kapa ai knowledge sources for "capture hubspot common issues"
If Kapa MCP is not configured, the user can set it up: https://docs.estuary.dev/features/mcp-integration/
This skill provides the flowctl workflow and troubleshooting that docs don't cover.
Step 1: Gather Requirements
Before writing any YAML, ask the user:
-
HubSpot account access? — User must have access to the HubSpot account being captured
-
OAuth credentials? — The connector authenticates with HubSpot via OAuth using
client_id+client_secret+refresh_token. The easiest path is to complete the OAuth flow in the Estuary web UI (it mints therefresh_tokenfor you), then pull the spec to local. Building your own HubSpot OAuth app and exchanging an auth code for a refresh token manually is supported but more involved.The connector's JSON schema also exposes a
Private App Credentialsdiscriminator, but in practice HubSpot Private App tokens have not been observed to authenticate successfully against the connector — use OAuth. -
Non-default data plane? — Most users use the default. Ask if they need a non-default data plane.
-
Which resources to capture? — All discovered resources (default) or a subset. The connector auto-discovers: Campaigns, Companies, Contact List Memberships, Contact Lists, Contacts, Custom Objects, Deal Pipelines, Deals, Email Events, Engagements, Feedback Submissions, Form Submissions, Forms, Goals, Line Items, Marketing Emails, Marketing Events, Orders, Owners, Products, Properties, Tickets, Workflows.
-
Capture property history? — Off by default. Enable to include historical changes to HubSpot object properties in captured documents.
-
Calculated property refresh schedule? — Per-binding cron. The web UI pre-fills
55 23 * * *(daily at 23:55 UTC), but the connector's spec default is""(disabled) — set the cron explicitly if you want refreshes. See note below. -
Custom objects naming? — Off by default. The hidden
useLegacyNamingForCustomObjectsfield isfalseby default, which prefixes custom object bindings withcustom_(e.g.,custom_form_submissions) to avoid collisions with standard objects. Do not change without contacting Estuary Support — it affects discovered resource and collection names.
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.
- 10d ago First seen · 321 lines · 77 tokens per session scan A 7588c23ce44e
capture-hubspot-create is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 20d ago), licensed Apache-2.0. It adds 77 tokens to every session and 3,827 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-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…
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…