CocoIndex is an incremental data-processing engine that keeps code, documents, messages, PDFs, and videos continuously updated as context for AI agents and language-model applications. Engineers use it to build declarative Python pipelines that process only changed data, and its catalogue skills help coding agents work with CocoIndex correctly.
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 cocoindex-io/cocoindex --skill target-connectorgit clone --depth 1 https://github.com/cocoindex-io/cocoindexWrote 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/cocoindex-io/cocoindex/target-connector)<a href="https://agentmods.dev/skills/cocoindex-io/cocoindex/target-connector"><img src="https://agentmods.dev/badge/skills/cocoindex-io/cocoindex/target-connector/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/cocoindex-io/cocoindex/target-connector"><img src="https://agentmods.dev/badge/skills/cocoindex-io/cocoindex/target-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.04646 |
| Opus 5.5 | $0.00021 | $0.01858 |
| Sonnet 5.5 | $0.00010 | $0.00929 |
| Haiku 4.5 | $0.00005 | $0.00465 |
Grade A, and why
target-connector 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 4d 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 — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Target Connector
Overview
A target connector connects CocoIndex's declarative target state system to external systems. It handles synchronization by determining what changed and applying changes to the external system.
When to Use
Use this skill when creating a new target connector for any external system (databases, file systems, cloud storage, APIs, etc.).
Key Data Types
What You Implement
| Type | Purpose |
|---|---|
TargetHandler |
Implements reconcile() — compares desired state with previous tracking records. Optionally implements attachment(att_type) for auxiliary child states. |
TargetActionSink |
Executes actions against the external system |
| Tracking Record | Persisted state for change detection (typically a frozen dataclass) |
| Action | Describes what operation to perform on the external system |
What CocoIndex Provides
| Type | Purpose |
|---|---|
TargetStateProvider |
Factory that creates TargetState objects from your handler |
TargetState |
Wrapper that holds the key and spec |
register_root_target_states_provider() |
Registers a root handler and returns a provider |
declare_target_state() |
Declares a leaf target state for reconciliation |
declare_target_state_with_child() |
Declares a target state and returns a child provider |
Implementation Workflow
Root Target States
- Define types: Key, Spec, TrackingRecord, Action
- Implement TargetHandler: The
reconcile()method must be non-blocking and free of side effects - Create TargetActionSink: Use
TargetActionSink.from_fn()orfrom_async_fn(). The callback receivescontext_provider: ContextProvideras its first positional argument, followed byactions, and returnsNone. A container target's sink also passeschild_handler=(see below) - Register provider: Call
register_root_target_states_provider(name, handler) - Create user-facing API: Wrap the provider in a user-friendly class
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.
- 4d ago Changed · +21 lines 3e1435c258b8
- 21d ago Changed · +2 lines 1d49834e5d4e
- 22d ago Changed · +2 lines 0bb2af6a58d2
- 1mo ago Changed · +27 lines 35b6ac24e698
- 1mo ago Changed · +14 lines 7bd6d2b7f7b2
- 1mo ago First seen · 400 lines · 52 tokens per session scan A c730a11d8c4c
target-connector is a skill published in the GitHub repository cocoindex-io/cocoindex (11,754 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 4,646 once invoked, about $0.0002 per session on Opus 5.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
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
azure-messaging-webpubsubservice-py
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns. Triggers: "azure-messaging-webpubsubservice", "WebPubSubServiceClient", "real-time", "WebSocket", "pub/sub".