A Graphite command that downloads a teammate’s Git branch and the branches it builds on into your local repository. Downloaded branches are read-only by default until you unfreeze them.

Use it to fetch a teammate’s branch stack, review it without editing, or continue the stack and submit your own pull request.

It avoids manually finding and fetching every branch in a stacked change. You can review a teammate’s work locally or add your own branch on top of it.

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

Your own site

<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/get"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/get/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/get"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/get.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 368 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.00368
Opus 5	$0.00006	$0.00184
Sonnet 5	$0.00003	$0.00074
Haiku 4.5	$0.00001	$0.00037

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

Security

Grade A, and why

get 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/get.md · 35 lines

What it actually says

Pull a teammate's branch (and its full stack) into the local repo so you can review, extend, or build on top. User input: $ARGUMENTS.

Steps

Confirm the working tree is clean (git status --short). If not, ask the user to commit or stash first.
Run gt get <branch>. Graphite fetches the branch and every ancestor up to trunk, tracking each one.
Branches arrive frozen by default — local edits are blocked until they're unfrozen. To start contributing immediately, run with --unfrozen.
Run gt ls to show the user the new stack alongside any existing local stacks.

After fetching

To extend a teammate's stack:

gt co <their-branch>             # navigate to it
gt unfreeze <their-branch>       # if you'll modify it; otherwise skip
# make changes
gt create -am "your addition"    # stack your branch on top
gt submit                        # opens your own PR

To just review without editing, leave the branch frozen — gt sync will still keep it current with the remote.

Key flags

-d, --downstack — fetch only this branch's ancestors (default is full stack)
-u, --remote-upstack — also fetch children pushed by the teammate
--unfrozen — bring in unfrozen so local edits are immediately allowed
-f, --force — overwrite any local copies of the same branch

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 · 35 lines · 13 tokens per session scan A c239a171d614

Subscribe to this mod's changes

get 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 368 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.

Code review Git and workflow

get

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

After fetching

Key flags

What this file has done since we first saw it

Other commands, from other repositories

devkit.github.review-pr

speckit.spex.submit

git

merge-conflict-analysis

code-review

repo-audit