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 agentmods add skills/adarshp14/relay/graphitenpx skills add adarshp14/relay --skill graphitegit clone --depth 1 https://github.com/adarshp14/relayWhat 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 | $0.00068 | $0.02861 |
| Opus 5 | $0.00034 | $0.01430 |
| Sonnet 5 | $0.00014 | $0.00572 |
| Haiku 4.5 | $0.00007 | $0.00286 |
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.
This is a copy
100% identical to graphite — 0 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graphite CLI Command Reference
Prefer gt over git
Use gt commands instead of their git counterparts for commit and branch management. Raw git bypasses Graphite's stack metadata, leaving descendants un-restacked and the CLI's view of the stack out of sync.
| Instead of | Use |
|---|---|
git checkout -b <name> |
gt create <name> |
git commit -m "msg" |
gt modify -c -m "msg" |
git commit --amend |
gt modify --amend |
git commit -am "msg" |
gt modify -cam "msg" |
Why: gt keeps stack metadata consistent and auto-restacks descendant branches when a parent changes.
Interactivity (for agents)
Several commands are interactive by default and will hang without a TTY: gt modify, gt move, gt split, gt restack, gt checkout (no arg), gt submit.
- Always pass explicit args/flags:
gt move --onto <branch>,gt modify -m "msg",gt checkout <branch>,gt submit --no-interactive. - Add
--no-interactive(or--quiet) to skip prompts. - If a command genuinely needs input that can't be supplied via flags (e.g. complex rebase conflict resolution), stop and notify the user rather than guessing.
Rebase Conflicts
When gt restack, gt move, gt sync, etc. pause on a conflict:
git statusto find conflicted files.- Resolve the
<<<<<<</=======/>>>>>>>markers. - Stage with
gt add -A(orgit add <file>). - Run
gt continue— nevergit rebase --continue. Graphite tracks its own rebase state; using raw git desyncs it. - Verify the stack once continue completes (
gt log, run tests).
To bail out: gt abort.
Global Flags
--help- Show help for a command--cwd- Working directory for operations--debug- Write debug output--interactive/--no-interactive- Enable/disable prompts (default: enabled)--verify/--no-verify- Enable/disable git hooks (default: enabled)--quiet- Minimize output, implies--no-interactive
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 · 413 lines · 68 tokens per session scan A 6f6c8e5ee323
graphite is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 2,861 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to graphite, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
create-tutorial
Scaffold a new Membrane API Gateway tutorial in the api-gateway repo — the numbered self-teaching YAML under distribution/tutorials/ /, its support files and README links, and the matching auto-discovered integration test. Use whenever the user asks to create, add, write, or scaffold a tutorial (or a tutorial step)…
optimize-interceptor-docs
Rewrite the reference documentation of a Membrane config element so the page generated at membrane-api.io comes out clean, exact, and reference-style. Use whenever the user wants to write, improve, optimize, polish, or review the docs / Javadoc / @description / @yaml example of an interceptor, plugin, or any…
review-branch
Review the current git branch against master — code quality, refactoring opportunities, regressions, correctness, and test coverage — and print a severity-grouped markdown report. Use whenever the user asks to review the branch, review their changes against master, do a pre-PR / pre-merge review, or asks "is this…
membrane-config
Generate a Membrane API Gateway configuration example or snippet — an apis.yaml (default) or, when explicitly asked, a legacy proxies.xml. Use this whenever the user wants a config, example, or snippet for Membrane: routing a port to a backend, a flow with plugins (setHeader, rateLimiter, basicAuthentication, openapi…
release-notes
Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…
mcp2cli
Turn any MCP server, OpenAPI spec, or GraphQL endpoint into a CLI. Use this skill when the user wants to interact with an MCP server, OpenAPI/REST API, or GraphQL API via command line, discover available tools/endpoints, call API operations, or generate a new skill from an API. Triggers include "mcp2cli", "call this…