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 agentmods add skills/celigo/ai/managing-integrationsnpx skills add celigo/ai --skill managing-integrationsgit 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/managing-integrations)<a href="https://agentmods.dev/skills/celigo/ai/managing-integrations"><img src="https://agentmods.dev/badge/skills/celigo/ai/managing-integrations.svg" alt="Measured on agentmods" 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 | $0.00120 | $0.04341 |
| Opus 5 | $0.00060 | $0.02171 |
| Sonnet 5 | $0.00024 | $0.00868 |
| Haiku 4.5 | $0.00012 | $0.00434 |
Grade A, and why
managing-integrations 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Integrations
An integration is a first-class Celigo resource that represents a named group of related resources -- flows, APIs, Tools, registered connections, scripts, settings, notification subscriptions, aliases, and revision history. It is the organizational layer that says "this body of automation goes together," typically because it serves a specific business purpose (the "Shopify-NetSuite integration", the "customer-onboarding integration"). The actual work is done by the resources inside; the integration coordinates how they are managed, deployed, and evolved.
Users may call integrations tiles, workspaces, or integration folders -- treat these as equivalent vocabulary for the same resource type.
Concerns when managing integrations:
- Organization and access -- grouping related work so it can be named, permissioned, and reported on as a unit. The integration boundary is the permission boundary.
- Plain vs Integration App -- customer-built integrations you own end to end, vs template-driven apps installed from the Marketplace.
- Hierarchy -- parent/child integrations for multi-store, multi-tenant, or per-environment splits.
- Lifecycle and promotion -- cloning across environments and running the ILM workflow (snapshots, pulls, reverts) to evolve integrations safely.
- Composition -- what lives inside, and how to move a resource from one integration to another.
- Per-integration knobs -- notifications, aliases, analytics, and settings that live on the integration record itself.
What Lives Inside an Integration
An integration is a container for the resources that do the work:
- Flows -- the body of the integration's automation; each is enabled/disabled independently.
- APIs -- HTTP endpoints the integration exposes to external callers.
- Tools -- reusable processing blocks invoked by flows, APIs, and AI agents.
- Registered connections -- connections attached to the integration's connection list (registration is organizational, not binding -- see Gotchas).
- Scripts -- JavaScript attached to the integration or its resources.
- Settings and custom forms -- the integration record holds the settings values; a custom form controls their shape.
What ships with it
1 file 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 First seen · 264 lines · 120 tokens per session scan A 3bb0654c3446
managing-integrations is a skill published in the GitHub repository celigo/ai (3 stars, last pushed today), licensed MIT. It adds 120 tokens to every session and 4,341 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-31.
Other skills, from other repositories
jira-ticket
Create a Jira issue via the Jira Cloud REST API. Requires JIRABASEURL, JIRAEMAIL, and JIRAAPITOKEN environment variables on the server. Trigger on: create a Jira ticket, raise a Jira issue, log a bug in Jira, open a story.
servicenow-ticket
Create a ServiceNow incident via the Table API. Requires SERVICENOWINSTANCE, SERVICENOWUSER, and SERVICENOWPASSWORD environment variables on the server. Trigger on: create a ServiceNow incident, raise an ITSM ticket, log an incident.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
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.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.