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 rome-os/rome --skill composio-cligit clone --depth 1 https://github.com/rome-os/romeWrote 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/rome-os/rome/composio-cli)<a href="https://agentmods.dev/skills/rome-os/rome/composio-cli"><img src="https://agentmods.dev/badge/skills/rome-os/rome/composio-cli/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/rome-os/rome/composio-cli"><img src="https://agentmods.dev/badge/skills/rome-os/rome/composio-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 145 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Rogue Agent · line 113 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00139 | $0.02666 |
| Opus 5.5 | $0.00056 | $0.01066 |
| Sonnet 5.5 | $0.00028 | $0.00533 |
| Haiku 4.5 | $0.00014 | $0.00267 |
Grade A, and why
composio-cli 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composio CLI
Preflight: Is The User Logged In?
Before running any toolkit command, confirm the user is logged in. If they are not, stop and tell them to log in — do not improvise.
composio whoami # exits non-zero when there is no session
If whoami fails (no Composio session), the user is logged out. Stop here. Do not:
- run
composio loginyourself, - look for an alternate toolkit, slug, or
proxyroute, - ask the user to paste a key, or
- attempt any other workaround.
Respond directly to the user with one message: they need to log in to Composio first, via the "Log in with Composio" action on the Composio app's dashboard. Then end your turn and wait — the request cannot proceed until they have logged in.
Only once whoami succeeds do you continue to the workflow below.
Connection Invariant: One Account Per Toolkit
Rome operates exactly one connected account per toolkit. This is load-bearing
because execute, proxy, and run have no flag to choose an account — they
act on the toolkit's single connected account, and when more than one exists
Composio silently resolves a non-deterministic default. You cannot tell, and
cannot control, which account a tool ran as. A second Gmail means a "send email"
might go out from the wrong account with no signal.
To keep every tool call deterministic:
- Never create a second account for a toolkit. Do not pass
--aliastocomposio linkto add an additional account, and do not enable themulti_accountexperimental feature. The alias buys you nothing on execution — there is no--alias/--accountonexecute— it only lets you accumulate ambiguous accounts. - Check before linking.
composio link <toolkit> --listshows existing accounts. If one isACTIVE, you are connected — retryexecute, do not link again. - If
--listshows more than one account for a toolkit, stop and surface it. Tell the user the toolkit has duplicate accounts and tool calls are ambiguous until the extras are removed. Do not guess which one to use.
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 · 240 lines · 139 tokens per session scan A efcfaacd6942
composio-cli is a skill published in the GitHub repository rome-os/rome (835 stars, last pushed today), licensed MIT. It adds 139 tokens to every session and 2,666 once invoked, about $0.0006 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
aos-router
Route one inbound user message to exactly one enabled AOS capability. This skill is a strategy contract only. Transport normalization, queueing, permissions, idempotency, audit events, retries, and capability execution stay in Rust.
code-studio-spec
Kiro-style Spec Mode for Code Studio: requirements, design, tasks, implementation, verification, and final report. Runtime sessions, candidate workspaces, diff approval, tests, and cancellation stay in Rust.
watchdog
Parse natural-language WatchDog questions into structured AgentOps queries. This skill documents the intent contract. Rust rules, permission checks, action guards, and fallback answers remain authoritative.
code-studio-code
Cursor/Codex-style coding workspace contract for ordinary Code Mode. This skill documents the behavior expected from the coding agent. Runtime sessions, workspace isolation, process execution, diff validation, and apply/reject actions stay in Rust.
nl2sql-reference
Strategy contract for user-bound reference files in Data Exploration. References can be README files, SQL demos, Python scripts, notebooks exported as text, metric dictionaries, or any UTF-8 text that explains business query patterns. Storage, upload validation, SQL safety, datasource permissions, and query execution…
pm-assistant
Product operations assistant strategy contract. PM short answers and deep analysis should be evidence-grounded and should separate facts from hypotheses. Model calls, hooks, queueing, cancellation, notifications, and staged task execution stay in Rust.