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/composiohq/composio/cli-releasenpx skills add ComposioHQ/composio --skill cli-releasegit clone --depth 1 https://github.com/ComposioHQ/composioWhat 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.00095 | $0.00451 |
| Opus 5 | $0.00048 | $0.00226 |
| Sonnet 5 | $0.00019 | $0.00090 |
| Haiku 4.5 | $0.00010 | $0.00045 |
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 2d 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/clior@composio/cli-local-tools; both packages are 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.
- 2d 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,003 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 451 once invoked, about $0.0005 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-30.
Other skills, from other repositories
final-release-review
Perform pre-release planning or a final release-candidate review for openai-agents-python by comparing the target with the previous remote tag, determining the minimum compatible release type, auditing regressions and contract changes, reviewing open documentation PR coverage, drafting minor-release Key Changes, and…
release-candidate-prep
Preflight and prepare an OpenAI Agents Python release candidate in a dedicated worktree from exact origin/main, gate readiness before branch creation, freeze the released API contract, create or replace the local release branch with one release commit, enforce final release review as a checker, and produce…
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…