gt-workflow

A repository workflow that uses Graphite, a tool for managing Git branches and commits, instead of Git commands.

In plain words
What is it for?
Use it to stage files, create branches with commits, amend changes, switch branches, synchronize branch stacks, and submit pull requests.
Why use it?
It provides the commands and sequence needed to create, update, synchronize, and submit changes when this repository requires Graphite.

Command for Cursor

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.

agentmods
npx agentmods add commands/vercel/next.js/gt-workflow
Clone the repo
git clone --depth 1 https://github.com/vercel/next.js

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 865 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00865
Opus 5 $0.00000 $0.00432
Sonnet 5 $0.00000 $0.00173
Haiku 4.5 $0.00000 $0.00086

Measured 2d ago against content hash d231aacad40e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gt-workflow 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 2d 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.

.cursor/commands/gt-workflow.md · 103 lines

How it starts

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

Git Workflow with Graphite

Overview

Use Graphite (gt) instead of git for ALL branch and commit operations in this repository.

Use gt Instead of git

All git commands work with gt. Always use gt instead of git:

gt add <files>       # instead of git add
gt commit            # instead of git commit
gt status            # instead of git status
gt diff              # instead of git diff
# etc.

For branch/push operations, use the Graphite-specific commands:

  • gt create <branch-name> -m "message" instead of git branch + git commit
  • gt submit --no-edit instead of git push

Graphite Commands

Command Description
gt add <files> Stage files for commit
gt create <branch-name> -m "message" Create a new branch with commit
gt modify -a --no-edit Stage all and amend current branch's commit
gt checkout <branch> Switch branches
gt sync Sync and restack all branches
gt submit --no-edit Push and create/update PRs
gt log short View stack status

Creating a New Branch with Changes

CRITICAL: Always stage changes BEFORE running gt create. The command format is:

gt add <files>                               # Stage changes FIRST
gt create <branch-name> -m "commit message"  # Then create branch with commit

If you run gt create without staged changes, it creates an empty branch with no commit. Then gt modify -a --no-edit will fail because there's no commit to amend.

If you accidentally created an empty branch:

gt add <files>
gt commit -m "commit message"    # Create initial commit
gt submit --no-edit              # Then submit

Read the full file on GitHub · 103 lines

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. 2d ago First seen · 103 lines · 0 tokens per session scan A d231aacad40e

Subscribe to this mod's changes

gt-workflow is a command published in the GitHub repository vercel/next.js (142,020 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 865 tokens. 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-30.