api-update

A command workflow for finding open pull requests in Composio's TypeScript and Python client repositories and planning SDK updates from them.

In plain words
What is it for?
Use it to inspect open client-library pull requests and determine what SDK code or types may need updating.
Why use it?
It turns proposed API changes into a reviewable update plan, including changed endpoints, parameters, types, and breaking changes.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/composiohq/composio/api-update
Clone the repo
git clone --depth 1 https://github.com/ComposioHQ/composio

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,152 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01152
Opus 5 $0.00000 $0.00576
Sonnet 5 $0.00000 $0.00230
Haiku 4.5 $0.00000 $0.00115

Measured 2d ago against content hash 205c5e0cb9d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-update 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.

.claude/commands/api-update.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Update Command

Check for open PRs in the Composio client repositories and create a plan for updating the SDKs.

Workflow

Step 1: Check for Open PRs

Fetch open PRs from both client repositories:

  1. TypeScript Client: github.com/composiohq/composio-base-ts
  2. Python Client: github.com/composiohq/composio-base-py

Use the GitHub CLI (gh) to list open PRs:

gh pr list --repo composiohq/composio-base-ts --state open --json number,title,url,headRefName,body
gh pr list --repo composiohq/composio-base-py --state open --json number,title,url,headRefName,body

Step 2: Get PR Patches

For each open PR, fetch the diff/patch to understand the changes:

gh pr diff <PR_NUMBER> --repo composiohq/composio-base-ts
gh pr diff <PR_NUMBER> --repo composiohq/composio-base-py

Step 3: Analyze Changes

For each PR, analyze the diff to identify:

  1. New API endpoints - New methods/functions added to the client
  2. Modified parameters - Changes to existing function signatures
  3. Deprecated endpoints - Removed or deprecated functionality
  4. Type changes - Updates to type definitions/schemas
  5. Breaking changes - Any backward-incompatible changes

Step 4: Identify SDK Impact

Map client changes to SDK files that need updates:

TypeScript SDK (@composio/core):

  • Check ts/packages/core/src/ for affected code
  • Types: ts/packages/core/src/types/
  • Models: ts/packages/core/src/models/
  • Services: ts/packages/core/src/services/

Important - Naming Convention for TypeScript: The API uses kebab-case (e.g., connected-accounts, auth-configs, tool-router) but the TypeScript SDK uses camelCase (e.g., connectedAccounts, authConfigs, toolRouter).

When mapping API changes to TypeScript SDK:

  • Convert all kebab-case parameter names to camelCase
  • Convert all kebab-case property names to camelCase
  • Keep the original kebab-case names in comments for reference to the API
  • Example: API's callback_url or callback-url becomes callbackUrl in TypeScript

Read the full file on GitHub · 139 lines

Changes

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.

  1. 2d ago First seen · 139 lines · 0 tokens per session scan A 205c5e0cb9d0

Subscribe to this mod's changes

api-update is a command published in the GitHub repository ComposioHQ/composio (30,003 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,152 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.