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 celigo/ai --skill configuring-exportsgit clone --depth 1 https://github.com/celigo/aiWrote 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/celigo/ai/configuring-exports)<a href="https://agentmods.dev/skills/celigo/ai/configuring-exports"><img src="https://agentmods.dev/badge/skills/celigo/ai/configuring-exports.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk 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.00059 | $0.06987 |
| Opus 5 | $0.00030 | $0.03494 |
| Sonnet 5 | $0.00012 | $0.01397 |
| Haiku 4.5 | $0.00006 | $0.00699 |
Grade A, and why
configuring-exports 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 3d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring Exports
An export is the data source in a Celigo integration. It connects to an external system and pulls data into the pipeline. Exports serve two roles:
- Source -- the starting point that fetches the primary batch of records
- Lookup -- a mid-flow enrichment step (
isLookup: true) that fetches additional data per-record during processing
Both roles are used across flows, APIs, and tools.
Beyond fetching data, exports also handle post-retrieval processing before records enter the pipeline:
- Output filter -- expression-based filtering to skip records that don't match criteria
- Transform -- Transformation 2.0 expression rules to reshape/flatten response data before mapping
- preSavePage hook -- JavaScript processing on the full page of records before they enter the pipeline
- One-to-many -- when used as a lookup, fan out child records from a parent. Set
oneToMany: trueandpathToManyto the child array path so each child triggers a separate lookup. Once fanned out, the array element itself is the record -- see One-to-many fan-out - Response mapping -- when used as a lookup, extract fields from the lookup response back into the record. Configured on the flow's
pageProcessors[]entry, but planned when building the lookup export. The response contains adataarray and anerrorsarray. Usedata[0].fieldNamewhen you expect a single result (e.g., fetching one order by ID). When multiple results are expected, map the whole array withextract: "data"(downstream steps then read it as a normal JSON array, or fan out over it with one-to-many), or use alistsentry withdata[*].fieldNameextracts to build a reshaped array. Do not putdata[*].fieldNamein a top-levelfields[].extract-- the wildcard is silently ignored there and nothing is merged. See writing-mappings > Response Mapping Reference. Response mapping uses Transformation 1.0 syntax (extract/generate pairs), not the newer expression-based transforms - postResponseMap hook -- JavaScript processing after response mapping merges the lookup response back into the record. Configured on the flow's
pageProcessors[]entry, but planned when building the lookup export
What ships with it
26 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.
- references/schemas/as2.yml 4.9 KB
- references/schemas/clone-request.yml 872 B
- references/schemas/clone-response.yml 695 B
- references/schemas/delta.yml 15 KB
- references/schemas/distributed.yml 1.9 KB
- references/schemas/dynamodb.yml 13 KB
- references/schemas/file.yml 121 KB
- references/schemas/filesystem.yml 929 B
- references/schemas/ftp.yml 5.5 KB
- references/schemas/group-by.yml 1.6 KB
- references/schemas/http.yml 81 KB
- references/schemas/jdbc.yml 7.2 KB
- references/schemas/mock-output.yml 2.8 KB
- references/schemas/mongodb.yml 12 KB
- references/schemas/netsuite.yml 192 KB
- references/schemas/once.yml 5.4 KB
- references/schemas/preview-request.yml 611 B
- references/schemas/preview-response.yml 1.2 KB
- references/schemas/rdbms.yml 7.7 KB
- references/schemas/request.yml 3.9 KB
- references/schemas/response.yml 2.7 KB
- references/schemas/s3.yml 6.4 KB
- references/schemas/salesforce.yml 52 KB
- references/schemas/test.yml 1.2 KB
- references/schemas/webhook.yml 53 KB
- references/schemas/wrapper.yml 1.7 KB
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.
- 3d ago Changed 7beb8a0e4a41
- 8d ago First seen · 393 lines · 59 tokens per session scan A 64780c9ba614
configuring-exports is a skill published in the GitHub repository celigo/ai (3 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 6,987 once invoked, about $0.0003 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-31.
Other skills, from other repositories
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
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 and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
developing-genkit-tooling
Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.