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 verify-changegit 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/verify-change)<a href="https://agentmods.dev/skills/composiohq/composio/verify-change"><img src="https://agentmods.dev/badge/skills/composiohq/composio/verify-change/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/verify-change"><img src="https://agentmods.dev/badge/skills/composiohq/composio/verify-change.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00336 |
| Opus 5.5 | $0.00023 | $0.00134 |
| Sonnet 5.5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
verify-change 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 yesterday.
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
Verify Change
Write agent-tooling scripts and tests in TypeScript and execute them with Bun; do not add .mjs or Node entrypoints. Existing SDK languages and package-management commands keep their repository ownership.
Use the verification map to select the existing checks and preserve a task's goal, authority, next step and blockers across sessions.
- For substantial work, initialize one task with the requested outcome and a matching profile. Keep the actual user request authoritative.
- Inspect
statuswhen resuming, updatenextStepandblockerin its localtask.json, and refresh external issue, PR and CI state before acting. - Run the profile after implementation. Read the receipt and its boundary before reporting what passed. A passing profile establishes only its named checks.
- Treat a recurring intervention as a candidate for an existing behavioral test, type or lint check. Prove the check rejects the original mistake. Preserve one-off judgment locally instead of expanding global instructions.
Do not create task records for trivial edits. Private task data and command output
stay under ignored .artifacts/; never attach them wholesale to a PR. This tool
records context and evidence, and does not grant commit, push, merge or release
authority.
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.
- yesterday First seen · 27 lines · 57 tokens per session scan A 312196218f08
verify-change is a skill published in the GitHub repository ComposioHQ/composio (30,836 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 336 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-10-30.
Other skills, from other repositories
dev-release-check
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
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.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.