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 desplega-ai/agent-swarm --skill composiogit clone --depth 1 https://github.com/desplega-ai/agent-swarmWrote 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/desplega-ai/agent-swarm/composio)<a href="https://agentmods.dev/skills/desplega-ai/agent-swarm/composio"><img src="https://agentmods.dev/badge/skills/desplega-ai/agent-swarm/composio/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/desplega-ai/agent-swarm/composio"><img src="https://agentmods.dev/badge/skills/desplega-ai/agent-swarm/composio.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.00128 | $0.03030 |
| Opus 5.5 | $0.00051 | $0.01212 |
| Sonnet 5.5 | $0.00026 | $0.00606 |
| Haiku 4.5 | $0.00013 | $0.00303 |
Grade A, and why
composio 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 1mo 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composio
Hub skill for Composio-managed third-party app access from the swarm. Three call surfaces are available when the deployment has enabled them:
- CLI:
agent-swarm x composio <METHOD> <path> [--body '<json>'] - MCP:
swarm_xwithtarget: "composio" - Script connection:
ctx.api.composio.<operationId>(args)inside a swarm script
COMPOSIO_API_KEY is deployment-scoped and injected by the CLI/API process — you
never pass or see it. All paths are relative Composio REST paths.
Per-app playbooks (verified slugs + argument shapes + gotchas): [[composio-gmail]] · [[composio-google-calendar]] · [[composio-google-docs]]. Read the sibling skill for the app you're touching — it lists the verified tool slugs so you don't have to
/searchblind.
Core Model
user_idis the app user whose connected accounts are used. A deployment commonly uses the person's email asuser_id(for example,<connected-account-email>). Resolve it with the procedure below. There is no explicit "create user" call — a user is created implicitly the first time you reference itsuser_id(e.g. when you create a Connect Link). Don't look for aPOST /usersendpoint; it doesn't exist in this flow.- Auth config (
ac_…) = a project-level OAuth app config (one per toolkit, set up in the Composio dashboard). A project can have several. - Connected account (
ca_…) = a specific user's authorized connection to a toolkit. Persists across sessions under thatuser_id. - Connect Link = the short-lived URL the user clicks to authorize OAuth.
- Tool Router session = a task/conversation runtime context that auto-resolves
the right connected account for a toolkit set. Reuse its
session_id; create a new one if the user, toolkit set, auth config, or pinned account changes.
Resolve the user and connected account
Do this before substituting any user_id or connected_account_id placeholder:
- Read the current task details and take its
requestedByUserId. - Call
resolve-userwithuserId: "<requestedByUserId>". Inspect the returnedexternalIdsforkind: "composio"; that entry'sexternalIdis the Composiouser_id. - List connected accounts filtered by that resolved value:
GET /connected_accounts?user_id=<resolved-composio-user-id>. Select the requested toolkit'sACTIVErow and use itsidasconnected_account_id. - If the task has no requester, the requester has no Composio identity, or the
filtered result is ambiguous, run
GET /connected_accountswithout a filter and compare the returned toolkit and user identity fields. If more than one account is still plausible, ask which identity/account to use. Never guess from another task's example.
What ships with it
2 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.
- 1mo ago First seen · 245 lines · 128 tokens per session scan A 3f23c79d5b13
composio is a skill published in the GitHub repository desplega-ai/agent-swarm (932 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 3,030 once invoked, about $0.0005 per session on Opus 5.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
security-observability
A read-only tool for examining security events already saved by agent-sec-cli, a command-line security log. It can connect those events to an agent session, run, or trace.
add-backend
Guide for adding a backend (Rust or Python) to the agent-sec-core security middleware. Use when creating new backends, integrating Rust or Python code into the security middleware, or extending with new backend actions.
skill-ledger
A security record for agent skills, which are reusable instruction packages for coding agents. It shows their status, reviews risk exposure, and can certify them with quick or user-approved deeper scans.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
prompt-scanner
A scanner for text sent to an AI agent, looking for prompt injection and jailbreak attempts. Prompt injection is text that tries to override an agent's instructions; a jailbreak tries to bypass its safety limits.