A workflow for creating a GitHub pull request for a Composio SDK repository. It gathers branch changes, links the request to a Linear issue tracker item, and formats the title and description.

Use it when preparing a Composio SDK change for review on GitHub, including feature work, bug fixes, tests, documentation, or maintenance.

It removes the need to manually inspect commits and write a consistent pull-request summary. It also helps keep the request tied to the issue being addressed.

composio-pr — Skill for Claude Code and Codex by jkomyno

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.

Any agent

npx skills add jkomyno/.dotfiles --skill composio-pr

Clone the repo

git clone --depth 1 https://github.com/jkomyno/.dotfiles

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jkomyno/.dotfiles/composio-pr/github.svg)](https://agentmods.dev/skills/jkomyno/.dotfiles/composio-pr)

Your own site

<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/composio-pr"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/composio-pr/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/composio-pr"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/composio-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,300 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.01300
Opus 5	$0.00017	$0.00650
Sonnet 5	$0.00007	$0.00260
Haiku 4.5	$0.00003	$0.00130

Measured 12d ago against content hash 61aaad3ef00c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

composio-pr 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 12d 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.

target/home/.agents/skills/composio-pr/SKILL.md · 158 lines

How it starts

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

Composio PR

Create GitHub pull requests for the Composio SDK with conventional commit titles and structured descriptions.

Workflow

Step 1: Gather context

Collect information needed to build the PR:

Run git log main..HEAD --oneline to see all commits on the current branch
Run git diff main...HEAD --stat to understand which files and packages changed
Run git diff main...HEAD to read the actual changes
Check the branch name for clues (e.g., fix/gemini, feat/e2e-tests-deno)
Ask the user for the Linear issue ID if not obvious from branch name or commits

Step 2: Determine the PR title

Build a conventional commit title following this format:

<type>(<scope>): <short imperative description>

Type (pick one):

feat — new feature or capability
fix — bug fix
refactor — code restructuring without behavior change
chore — maintenance, deps, CI, tooling
docs — documentation only
test — adding or fixing tests
perf — performance improvement

Scope — the package or area affected:

ts/core or just core — core TypeScript SDK
ts/e2e — TypeScript e2e tests
py — Python SDK
docs — documentation (fern/)
Provider names: openai, anthropic, langchain, vercel, google, mastra
Use the most specific scope that covers all changes

Description rules:

Imperative mood ("add X", not "adds X" or "added X")
Lowercase after the colon
No period at the end
Under 70 characters total
Use backticks for code references (e.g., `connected_account.refresh()`)

Examples:

feat(py): add support for \connected_account.refresh()``
fix(core): loosen V3 webhook schema to accept any composio.* event type
refactor(ts/e2e): remove deprecated \nodeVersions` property`
feat(ts/e2e): add Node.js e2e test about file roundtrip

Step 3: Write the PR description

The description follows a strict structure. See references/pr_examples.md for real examples from merged PRs.

Read the full file on GitHub · 158 lines

Files

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.

references/pr_examples.md 4.0 KB

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.

12d ago First seen · 158 lines · 35 tokens per session scan A 61aaad3ef00c

Subscribe to this mod's changes

composio-pr is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 7d ago), licensed MIT. It adds 35 tokens to every session and 1,300 once invoked, about $0.0002 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-31.

Git and workflow

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens