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 agents/composiohq/composio/connect-clients-syncgit clone --depth 1 https://github.com/ComposioHQ/composioWrote 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/agents/composiohq/composio/connect-clients-sync)<a href="https://agentmods.dev/agents/composiohq/composio/connect-clients-sync"><img src="https://agentmods.dev/badge/agents/composiohq/composio/connect-clients-sync.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.00000 | $0.01327 |
| Opus 5 | $0.00000 | $0.00664 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
connect-clients-sync 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect Clients Sync
Syncs AI client definitions from the dashboard repo (ComposioHQ/composio_dashboard) to the Composio Connect docs page.
When This Runs
Triggered by repository_dispatch from dashboard production deploys, or manually via workflow_dispatch. Creates a PR if client definitions have changed.
Source of Truth
The dashboard repo's client definitions file:
ComposioHQ/composio_dashboard
src/app/(connect)/[org]/~/connect/clients/_components/client-definitions.ts
This file contains the ALL_CLIENTS array with every client's:
id,name,description,icon,categoryauthMethodswith step-by-step setup instructions- Auth types:
oauthand/orapi-key
Target File
docs/content/docs/composio-connect.mdx
Process
- Fetch
client-definitions.tsfromComposioHQ/composio_dashboard(main branch) using the GitHub API - Read the current
docs/content/docs/composio-connect.mdx - Compare the client list, categories, and setup steps
- If there are differences, update
composio-connect.mdxto match the dashboard
MDX Structure
The page uses <ConnectFlow> and <ConnectClientOption> components:
<ConnectFlow>
<ConnectClientOption id="client-id" name="Client Name" description="..." icon="/images/clients/logo.svg" category="popular|ide|other">
<Steps>
<Step>
<StepTitle>Step title</StepTitle>
Step description.
</Step>
</Steps>
</ConnectClientOption>
</ConnectFlow>
Category Mapping
Only these 4 clients should have category="popular" (shown as tabs):
claude-codecodexopenclawclaude-desktop
All other clients go in the dropdown:
- Dashboard
IDEscategory →category="ide" - Everything else →
category="other"
Auth Method Selection
Show all auth methods from the dashboard. When a client has both OAuth and API key methods, use <Tabs> to let the user choose:
<Tabs items={["OAuth (recommended)", "API Key"]}>
<Tab value="OAuth (recommended)">
<Steps>
<Step>
<StepTitle>Step title</StepTitle>
OAuth step content.
</Step>
</Steps>
</Tab>
<Tab value="API Key">
<Steps>
<Step>
<StepTitle>Get your API key</StepTitle>
Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
</Step>
<Step>
<StepTitle>Step title</StepTitle>
API key step content.
</Step>
</Steps>
</Tab>
</Tabs>
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 · 164 lines · 0 tokens per session scan A 53bc7d2debbe
connect-clients-sync is an agent published in the GitHub repository ComposioHQ/composio (30,036 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,327 tokens. 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 agents, from other repositories
agent-definitions
AgentDefinition is the new, lean, org-scoped agent config that replaces the legacy CrewAI tables.Agent model for graph execution. It carries identity and execution-tuning fields only — capabilities (tools, knowledge, storage access) are not columns on the model, they attach through Surfaces. Realtime (voice)…
AGENTS
This directory contains custom subagent definitions for Claude Code (and Cursor, which reads from this directory).
INSTALL
The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.
agent-service
Agent "agent-service" from EpicStaff/EpicStaff, covering agent service (src/agent/), 1. overview & entry point, 2. request flow, 3. contract / request models and agentrequest.
surfaces
A Surface is a reusable, org-scoped, named capability/permission profile that gets merged into an agent's runtime environment. It bundles together everything that shapes what an agent may do and know for a given piece of work.
architecture
Fetches or creates architecture tables for a Data Basis dataset on Google Drive. Each table in the dataset gets one Google Sheets file defining column names, types, descriptions, and metadata.