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 cocoindex-diagramsgit 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/cocoindex-diagrams)<a href="https://agentmods.dev/skills/cocoindex-io/cocoindex/cocoindex-diagrams"><img src="https://agentmods.dev/badge/skills/cocoindex-io/cocoindex/cocoindex-diagrams/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/cocoindex-diagrams"><img src="https://agentmods.dev/badge/skills/cocoindex-io/cocoindex/cocoindex-diagrams.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.00124 | $0.02176 |
| Opus 5 | $0.00062 | $0.01088 |
| Sonnet 5 | $0.00025 | $0.00435 |
| Haiku 4.5 | $0.00012 | $0.00218 |
Grade A, and why
cocoindex-diagrams 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 11d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CocoIndex Docs Diagrams
Inline SVG diagrams in the docs are authored as Astro components under
docs/src/components/diagrams/, composed from shape-semantic primitives
that share a palette and styling. Static .svg files exported from
design tools are legacy — always build new diagrams with the primitives.
When this skill applies
Apply this skill when:
- Adding a new diagram to a docs page (
.mdxunderdocs/src/content/docs/). - Editing or replacing an existing diagram component.
- Reviewing a rendered diagram for layout or style issues.
- Reworking a legacy
<img src="/docs/img/...svg">reference.
Do not apply for:
- Marketing-site diagrams under
cocoindex.github.io/(different style, different primitives). - General SVG editing outside
docs/src/components/diagrams/.
The canonical reference
Read docs/src/components/diagrams/README.md first. It documents the
shape vocabulary, palette vars, shared CSS classes, animation conventions,
directory layout, and MDX embedding pattern. This SKILL.md assumes that
reference is current — do not duplicate it here.
Then consult the three references bundled with this skill for the session-specific knowledge that isn't in the project README:
- references/workflow.md — the preview loop (headless Chrome + base-path gotcha), how to crop and view output, rebuild discipline.
- references/pitfalls.md — the traps that repeatedly cost iterations (dg-step opacity, color unification, magic-number insets, labels without auto-wrap).
- references/layout-patterns.md — layout idioms (horizontal arrows, symmetric padding, compactness, bindings vs arrows).
Core procedure
When asked to create or edit a diagram, proceed in this order:
1. Read the reference materials
Load docs/src/components/diagrams/README.md plus the three references
above. Skim, don't memorize — refer back when designing.
2. Design the layout before writing code
What ships with it
5 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.
- 11d ago First seen · 166 lines · 124 tokens per session scan A c9027653a607
cocoindex-diagrams is a skill published in the GitHub repository cocoindex-io/cocoindex (11,519 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 2,176 once invoked, about $0.0006 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
cli-command
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, @effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use…
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…
dstack-prototyping
Use with the dstack skill for model-serving work when the image, serving command, resources, backend/fleet choice, or service behavior is not proven. Guides task-first prototyping on real hardware, choosing fleets/backends that can reuse idle instances and caches, checking vLLM/SGLang sources, and verifying the final…
designing-vizro-layouts
Use this skill when designing or building Vizro dashboard layouts — grid configuration, component sizing, filter/parameter placement, selector types, or container patterns. Activate when the user is creating wireframes, defining page structure, placing controls, or sizing charts.
ui-mobile
Mobile UI patterns - React Native, iOS/Android, touch targets.