A command that sends a branch stack to the remote repository and creates or updates pull requests. A pull request is a proposal for merging code into another branch for review.

Use it to submit the current branch and its earlier branches, or the entire stack, and to update existing pull requests without opening new ones.

It avoids pushing each dependent branch and managing its pull request separately.

submit — Command for Claude Code by pleaseai

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.

Clone the repo

git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Or install graphite, the plugin that ships this one along with the rest of its 3 skills, 16 commands.

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/commands/pleaseai/claude-code-plugins/submit/github.svg)](https://agentmods.dev/commands/pleaseai/claude-code-plugins/submit)

Your own site

<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/submit"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/submit/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/commands/pleaseai/claude-code-plugins/submit"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 444 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.00013	$0.00444
Opus 5	$0.00006	$0.00222
Sonnet 5	$0.00003	$0.00089
Haiku 4.5	$0.00001	$0.00044

Measured yesterday against content hash fa581bddb1a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

plugins/graphite/commands/submit.md · 34 lines

What it actually says

Submit the current Graphite stack to the remote and open or update pull requests. User input: $ARGUMENTS.

Decide scope

Default gt submit pushes the current branch and everything downstack from it.
gt submit --stack (alias gt ss) pushes the entire stack rooted at trunk.
gt submit --stack --update-only (gt ss -u) updates PRs only — won't open new ones.

If the user didn't specify scope and the stack has more than one branch, ask whether they want --stack or just the current branch + downstack.

Steps

Run gt ls and show the user which branches will be submitted.
Run git status --short to confirm there are no uncommitted changes. If there are, ask whether to gt modify -a them in first, stash, or abort.
Run gt sync --no-pull or gt restack if gt ls shows any branch as needs restack — do not submit a stale stack.
Run the appropriate gt submit command. Pass -c / --confirm to skip interactive prompts only if the user asked for non-interactive.
Report each created/updated PR URL from the output.

Key flags

--stack — submit every branch in the stack (not just current + downstack)
--update-only, -u — update existing PRs, never create new ones
--draft — open as draft
-c, --confirm — skip the interactive prompts
-e, --edit — open $EDITOR for each PR description
-f, --force — force-push (use with care; Graphite already uses --force-with-lease by default)
--ai — Graphite drafts the PR title/body

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.

yesterday First seen · 34 lines · 13 tokens per session scan A fa581bddb1a2

Subscribe to this mod's changes

submit is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 444 once invoked, about $0.0001 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-09-07.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.

dsswift/ion · 25 tokens