agentmods.dev

checkout

checkout is a command for Claude Code from pleaseai/claude-code-plugins. It costs 17 tokens per session (374 once invoked), scanned A, original, MIT.

A Graphite command for moving between branches in a stacked Git workflow. It can move up or down the stack, jump to its top or bottom, switch to the main branch, or open a branch by name.

In plain words
What is it for?
Use it to switch branches, move through a stack by a chosen number of steps, or pull a teammate’s stack while changing branches.
Why use it?
It reduces the need to remember branch names and makes the order of dependent branches easier to navigate. This is especially useful when a stack has several branches.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the graphite plugin — 3 skills, 16 commands shipped together

not rated 13repo 2d ago A scan 17 tokens original MIT

Good fit Use it to switch branches, move through a stack by a chosen number of steps, or pull a teammate’s stack while changing branches.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pleaseai/claude-code-plugins/checkout
View source ↗ pleaseai/claude-code-plugins plugins.pleaseai.dev
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.

agentmods badge for checkout

README.md
[![agentmods](https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/checkout/github.svg)](https://agentmods.dev/commands/pleaseai/claude-code-plugins/checkout)
Your own site
<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/checkout"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/checkout/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.

agentmods 80×15 button for checkout

Your own site · 80×15
<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/checkout"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/checkout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 374 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00374
Opus 5 $0.00009 $0.00187
Sonnet 5 $0.00003 $0.00075
Haiku 4.5 $0.00002 $0.00037

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

Security

Grade A, and why

checkout 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/checkout.md · 30 lines

What it actually says

Move to a different branch in the Graphite stack. User input: $ARGUMENTS.

Dispatch by argument

  • up or empty + "next up" intent → gt up (alias gt u); accept a trailing number for steps (gt up 2).
  • down → gt down (gt d); same step semantics.
  • top → gt top (gt t).
  • bottom → gt bottom (gt b).
  • trunk or main → gt checkout --trunk (gt co -t).
  • A branch name → gt checkout <name> (gt co <name>).
  • Empty / no argument → gt checkout (interactive picker — only run if the session supports interactive prompts; otherwise show gt ls and ask the user to pick).

Steps

  1. If the working tree is dirty, run git status --short and confirm with the user — checkout will fail or carry the changes.
  2. Run gt ls to show context.
  3. Run the dispatched command.
  4. Confirm with gt ls (the new current branch is marked ◉).

Notes

  • When gt up or gt top hits a branch with multiple children, it prompts to disambiguate. In non-interactive contexts, pass the specific branch name instead.
  • gt checkout -s <branch> switches to a branch and pulls its whole stack — useful when navigating to a teammate's stack after gt get.
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. yesterday First seen · 30 lines · 17 tokens per session scan A 03893db0381f

Subscribe to this mod's changes

checkout is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 374 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
Related

Other commands, from other repositories

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 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

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

handoff

Export a Waybill Bundle by default, or import one when requested.

wardmos/waybill · 13 tokens