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 graphite-setupgit 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-setup)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/graphite-setup"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/graphite-setup.svg" alt="Measured on agentmods" 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.00161 | $0.02599 |
| Opus 5 | $0.00081 | $0.01300 |
| Sonnet 5 | $0.00032 | $0.00520 |
| Haiku 4.5 | $0.00016 | $0.00260 |
Grade A, and why
graphite-setup 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 today.
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.
This is a copy
86% identical to owasp-asvs — 472 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graphite — Repository Setup & CI Configuration
This skill is the counterpart to the graphite skill (CLI workflow). It covers the one-time and ongoing repository / GitHub / CI configuration that lets gt stacks merge cleanly. If the user is driving gt locally, use the graphite skill instead.
Source docs (cite when proposing changes):
- GitHub configuration guidelines
- Setup: merge queue integration
- Setup: recommended CI settings
- Stacking and CI
Onboarding a repo — do this in order
Work top-down. Each step has a checkpoint; if it fails, fix that step before moving on — a later step won't compensate for an earlier misconfiguration.
- Repo settings — disable the single-push branch limit, enable auto-delete head branches (GitHub repository settings).
- ✅ Checkpoint:
gt submit --stackon a 2-branch test stack pushes both branches without a "too many branches in one push" error.
- ✅ Checkpoint:
- Branch protection — turn off the four Graphite-breaking settings; keep the recommended safe ones (tables below).
- ✅ Checkpoint: open a test PR, approve it, then push an amend — the approval is not dismissed and the PR stays mergeable.
- CI triggers — add
branches-ignore: "**/graphite-base/**"and ensure CI runs on every stacked PR, not just trunk (CI configuration).- ✅ Checkpoint: push a 2-PR stack; both PRs get CI runs, and no job fails with "branch not found" on a
graphite-base/*ref.
- ✅ Checkpoint: push a 2-PR stack; both PRs get CI runs, and no job fails with "branch not found" on a
- Merge queue — pick exactly one mode (Merge queue: pick one); skip if you aren't using a queue.
- ✅ Checkpoint: only one queue is active — if you chose Graphite's, GitHub's native queue is off in branch protection.
- (Optional) CI Optimizations — only for teams with tall stacks and ≥~10 active stackers (CI Optimizations).
- ✅ Checkpoint: a known-skippable intermediate PR shows its CI skipped, while the base and top PRs still run.
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.
- today First seen · 179 lines · 161 tokens per session scan A f6c4857b0f75
graphite-setup is a skill published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed yesterday), licensed MIT. It adds 161 tokens to every session and 2,599 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to owasp-asvs, differing in 472 lines, and is treated as a copy.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.