Composio is a software toolkit that gives AI agents access to authenticated tools for interacting with apps and services. Developers use its SDKs, command-line interface, sessions, and sandbox to build agents that can carry out actions. The catalogue add-ons support workflows for using Composio with coding agents.
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 ComposioHQ/composio --skill cli-releasegit 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/skills/composiohq/composio/cli-release)<a href="https://agentmods.dev/skills/composiohq/composio/cli-release"><img src="https://agentmods.dev/badge/skills/composiohq/composio/cli-release/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/composiohq/composio/cli-release"><img src="https://agentmods.dev/badge/skills/composiohq/composio/cli-release.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.00095 | $0.00440 |
| Opus 5.5 | $0.00038 | $0.00176 |
| Sonnet 5.5 | $0.00019 | $0.00088 |
| Haiku 4.5 | $0.00010 | $0.00044 |
Grade A, and why
cli-release 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 17d 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.
What it actually says
CLI Release
Use this skill for the GitHub Release that powers the standalone composio binary and installer.
Read references/release-workflow.md before selecting a candidate or dispatching a workflow.
Release Contract
- Never add a Changeset for
@composio/cli; the package is ignored by Changesets and such files wedgets.release.yml. - Treat a merge to
nextthat touches CLI paths as a beta build. Promote a tested beta with thepromote-stableworkflow action for the normal stable-release path. - Never bump the private CLI
package.jsonto select a binary version. For an intentional minor or major, build an explicitly versioned beta and promote that tested beta through the same stable path. - Resolve beta tags and workflow state from GitHub immediately before acting. Never invent or reuse a stale candidate from memory.
- A stable promotion is a production write. If the user did not name the exact beta tag, present the resolved candidate and obtain explicit confirmation before dispatching it.
- Follow the release through asset verification and installation tests. Do not stop after the dispatch succeeds.
Execution
- Classify the request as automatic beta, manual beta, stable promotion, or recovery.
- Run the playbook's read-only preflight and identify the exact source commit and release tag.
- Dispatch only the requested workflow action and watch the resulting run to completion.
- Verify the published release and downstream checks named in the playbook.
- Report the released tag, source beta or commit, workflow URL, asset state, install-test result, and any remaining follow-up.
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.
- 17d ago Changed f3917c5fde4e
- 1mo ago First seen · 30 lines · 95 tokens per session scan A b289ffbefe21
cli-release is a skill published in the GitHub repository ComposioHQ/composio (30,595 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 440 once invoked, about $0.0004 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
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
git-workflow
Git workflow guidance for commits, branches, and pull requests.
skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-creator's retrofit, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
python-venv
Create or reuse a project-local Python virtual environment and ensure .venv is excluded by the repository's .gitignore.