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 python-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/python-release)<a href="https://agentmods.dev/skills/composiohq/composio/python-release"><img src="https://agentmods.dev/badge/skills/composiohq/composio/python-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/python-release"><img src="https://agentmods.dev/badge/skills/composiohq/composio/python-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.00053 | $0.00092 |
| Opus 5.5 | $0.00021 | $0.00037 |
| Sonnet 5.5 | $0.00011 | $0.00018 |
| Haiku 4.5 | $0.00005 | $0.00009 |
Grade A, and why
python-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 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.
What it actually says
Python Release
Use this skill for Python release and packaging work.
Read references/release-workflow.md before changing Python release metadata or generated client pins.
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.
- 1mo ago First seen · 11 lines · 53 tokens per session scan A d31936f37668
python-release is a skill published in the GitHub repository ComposioHQ/composio (30,574 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 92 once invoked, about $0.0002 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
python-venv
Create or reuse a project-local Python virtual environment and ensure .venv is excluded by the repository's .gitignore.
publish-python
Prepares and triggers a new Python package release: runs cleanup, validates semantic versioning, updates pyproject.toml and docs, builds with uv, creates a GitHub release, and monitors the publishing workflow. Supports patch/minor/major auto-increment. Use when the user wants to cut a release, bump the version, or…
dev-git-workflow
Use for non-trivial Git state such as branch strategy, worktrees, merge/rebase decisions, conflicts, reviewer-facing PR preparation, tags, and release notes. Do not trigger for a routine commit, push, or PR that needs no strategy decision.
dev-release-check
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
uv-package-manager
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.
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…