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.
npx skills add pleaseai/claude-code-plugins --skill graphitegit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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.
[](https://agentmods.dev/skills/pleaseai/claude-code-plugins/graphite)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/graphite"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/graphite/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.
<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/graphite"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/graphite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00108 | $0.02334 |
| Opus 5 | $0.00054 | $0.01167 |
| Sonnet 5 | $0.00022 | $0.00467 |
| Haiku 4.5 | $0.00011 | $0.00233 |
Grade A, and why
graphite 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graphite CLI (gt) — Stacked PR Workflow
Invoke the CLI as gt (not graphite). A stack is a chain of branches where each builds on its parent and maps to one PR.
When the user is in a Graphite repo (.git/.graphite_repo_config present) or mentions stacked PRs / gt / Graphite, prefer gt over raw git for branch creation, rebasing, and pushes. Plain git still works for staging, diffing, logs, and inspection.
Core mental model
- One commit per branch. Stack additional changes by creating new branches on top, not new commits on the same branch.
- Trunk is
main(or whatevergt initselected). Stacks are rooted on trunk. gtknows the parent of every tracked branch. It uses that metadata to restack automatically when ancestors change.- Do not use raw
git rebaseto move tracked branches. It can wipe Graphite metadata. Usegt modify,gt restack, orgt moveinstead.
The golden path: create → submit
# Make changes, then:
gt create -am "feat: add activity feed API" # stage all, commit, new branch
# More changes for the next layer:
gt create -am "feat: render feed in UI" # creates branch on top of previous
gt submit --stack # push all branches, open PRs
gt create [name]creates a branch from the current HEAD with the staged changes already committed. With-ait stages all changes; with-m "..."it sets the commit message; combined-am "..."is the common form.gt cis the alias forgt create.gt submitpushes the current branch and downstack;gt submit --stack(aliasgt ss) pushes every branch in the current stack and opens/updates PRs for each.
Viewing the stack
gt log # full tree with branches, PRs, worktree paths
gt ls # compact view (alias for `gt log short`)
The filled circle (◉) marks the current branch. Always run gt ls before any restack/move operation to confirm parent relationships.
Navigating the stack
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 · 197 lines · 108 tokens per session scan A 727b432681bb
graphite is a skill published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 2,334 once invoked, about $0.0005 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.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
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.
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.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.