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-importsgit 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-imports)<a href="https://agentmods.dev/skills/celigo/ai/configuring-imports"><img src="https://agentmods.dev/badge/skills/celigo/ai/configuring-imports.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.00051 | $0.06252 |
| Opus 5 | $0.00026 | $0.03126 |
| Sonnet 5 | $0.00010 | $0.01250 |
| Haiku 4.5 | $0.00005 | $0.00625 |
Grade A, and why
configuring-imports 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 7d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring Imports
An import is the data destination in a Celigo integration. It takes records from an upstream step and writes them to an external system -- REST APIs, databases, ERPs, file servers, or AI models. Every import is bound to exactly one connection and one adaptor type.
Imports handle six concerns:
- Field mapping -- transforming source fields into the destination system's expected format (including value resolution via static maps and lookup tables). Uses Mapper 2.0 (
mappings[]array) by default; NetSuite and Salesforce imports only support Mapper 1.0 (mapping.fields[]/mapping.lists[]) - Operation logic -- create, update, upsert, delete, attach/detach
- Hooks -- JavaScript pre/post processing at various pipeline stages (preMap, postMap, postSubmit). File-based imports that generate files from records also support postAggregate
- One-to-many -- fan out child records from a parent. Set
oneToMany: trueandpathToManyto the child array path (e.g.,"lineItems") when one source record should create multiple import operations - Response mapping -- extract fields from the import's API response back into the record for downstream steps. Configured on the flow's
pageProcessors[]entry, but planned when building the import. The response is available via_json(the raw API response) anderrors. Use_json.fieldNameto extract from the response (e.g.,_json.idfor a created record's ID,_json.output.1.content.0.textfor OpenAI responses). 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 response back into the record. Configured on the flow's
pageProcessors[]entry, but planned when building the import. Use to transform or enrich the merged record before downstream steps
Imports are used across flows, APIs, and tools.
Import Execution Pipeline
What ships with it
20 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/aiagent.yml 53 KB
- references/schemas/as2.yml 3.1 KB
- references/schemas/clone-request.yml 873 B
- references/schemas/clone-response.yml 661 B
- references/schemas/dynamodb.yml 23 KB
- references/schemas/file.yml 19 KB
- references/schemas/filesystem.yml 794 B
- references/schemas/ftp.yml 19 KB
- references/schemas/guardrail.yml 18 KB
- references/schemas/http.yml 59 KB
- references/schemas/jdbc.yml 9.3 KB
- references/schemas/mongodb.yml 4.8 KB
- references/schemas/netsuite.yml 10 KB
- references/schemas/netsuitedistributed.yml 50 KB
- references/schemas/rdbms.yml 45 KB
- references/schemas/request.yml 1.1 KB
- references/schemas/response.yml 2.3 KB
- references/schemas/s3.yml 18 KB
- references/schemas/salesforce.yml 136 KB
- references/schemas/wrapper.yml 3.8 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.
- 7d ago First seen · 340 lines · 51 tokens per session scan A 751a5b704d5e
configuring-imports is a skill published in the GitHub repository celigo/ai (3 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 6,252 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.