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 agentmods add commands/composiohq/composio/changeloggit 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/commands/composiohq/composio/changelog)<a href="https://agentmods.dev/commands/composiohq/composio/changelog"><img src="https://agentmods.dev/badge/commands/composiohq/composio/changelog.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
changelog 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 6d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check the changes between the current branch and next branch, and create a changelog file inside /docs/content/changelog in the file format of MM-DD-YY-<title>.mdx.
File Naming
MM-DD-YY.mdx # e.g., 12-29-25.mdx
MM-DD-YY-suffix.mdx # Multiple same day: 12-10-25-masking.mdx
Template
---
title: "Your Title Here"
description: "Brief description of the change"
date: "YYYY-MM-DD"
---
Brief intro paragraph explaining what changed.
### SDK Versions
| SDK | Version |
|-----|---------|
| Python | vX.Y.Z+ |
| TypeScript | vX.Y.Z+ |
### What Changed (if applicable)
**Before:**
```python
old_code()
After:
new_code()
Breaking Changes (if applicable)
What breaks and why.
What's New / Improvements / Bug Fixes
- Change 1
- Change 2
Backward Compatibility
Notes about backward compatibility.
## Rules
1. **Frontmatter required** - `title`, `description`, and `date` (YYYY-MM-DD format)
2. **No `#` heading** - Title renders automatically from frontmatter
3. **Use `###` for sections** - Content headings start at h3
4. **No emojis** - No checkmarks, warning symbols, etc. in prose (okay in code comments)
5. **TypeScript code blocks** - Add `// @noErrors` on first line to skip type checking
## Change Types
| Type | How to Format |
|------|---------------|
| Breaking Change | `<Callout type="warn">` + before/after code + migration guide |
| New Feature | `### What's New` |
| Improvement | `### Improvements` |
| Bug Fix | `### Bug Fixes` or inline description |
| Deprecation | `<Callout>` with timeline |
## Code Examples
For TypeScript code that shouldn't be type-checked:
```typescript
// @noErrors
const result = await composio.tools.get(userId);
For before/after comparisons, use labeled sections:
Before:
old_code()
After:
new_code()
Examples
Reference these existing changelogs for style:
- Bug fix:
01-21-26-initiate-active-status-filter.mdx - Breaking change:
01-14-26-auth-config-patch-semantics.mdx - New feature:
01-12-26-tool-router-improvements.mdx - Simple change:
01-30-26-simplified-optional-schemas.mdx
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.
- 6d ago First seen · 104 lines · 0 tokens per session scan A 8280e93a4fe5
changelog is a command published in the GitHub repository ComposioHQ/composio (30,071 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 tokens. 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 commands, from other repositories
type-coverage
Vérification Couverture des Types Python.
venv-health
../../workflows/venv-health.md.
generate-endpoint
Génération Endpoint FastAPI.
generate-model
Génération Model SQLAlchemy.
prepare-dataset
Analyse a raw data file (CSV, JSON, JSONL, TSV, Parquet) and generate a complete Python script scripts/dataset/ .py that inherits from BaseDatasetPreparer and transforms the file into a JSONL dataset ready for fine-tuning with Unsloth.
refactor-py-sdk
Command to refactor Python SDK.