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/stacknpx skills add adarshp14/relay --skill stackgit 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.00061 | $0.02114 |
| Opus 5 | $0.00030 | $0.01057 |
| Sonnet 5 | $0.00012 | $0.00423 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
stack 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
100% identical to stack — 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack
Use the local stack CLI for squash-safe stacked PR repair. It is designed for
repos where PRs are squash-merged and merged branches are deleted, so Git ancestry
alone cannot preserve stack intent.
Keep ordinary editing and commits on plain git. Use stack only for stack
intent, stack inspection, sync, merge, and undo workflows.
Mental Model
dev
└─ stack-a #101
└─ stack-b #102
└─ stack-c #103
Stack intent is persisted in .git/stack/state.json as stack links:
- branch
- parent branch
- merge-base anchor
- PR number
Mutating sync and merge workflows write .git/stack/undo.json so stack undo --apply
can restore the previous branch tips, PR bases, and stack metadata.
Common Commands
stack status: show the relevant tracked stack graph and include open PR details when GitHub is available.stack guide: print the opinionated happy path for agents and humans.stack track <branch> --onto <parent>: record stack intent for an existing branch.stack sync --dry-run [branch]: preview inferred PR-base stack links and repairs without changing branches or PRs.stack sync [branch]: infer clear PR-base stack links, repair descendants, retarget PRs, and refresh stack blocks. With a branch argument, sync only the stack containing that branch.stack sync --continue-on-failure/stack sync --keep-going: process independent stacks, summarize successes and failures, and exit nonzero if any stack failed.stack doctor: inspect local Git, GitHub, stack metadata, trunk branches, and undo journal health without changing anything.stack merge [branch]: dry-run root PR merge plus descendant repair.stack merge [branch] --apply: retarget immediate child PRs, squash-merge the root PR, then repair descendants.stack merge [branch] --auto: retarget immediate child PRs, enable GitHub auto-merge, wait, then repair descendants.stack merge --auto --through <branch-or-pr>: repeat auto-merge one root at a time until the target branch or PR lands.stack history: show the most recent applied repair journal.stack undo: dry-run restore of the most recent applied repair.stack undo --apply: restore branches, PR bases, and stack metadata from the journal.
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 · 222 lines · 61 tokens per session scan A 6c567927a8fe
stack is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 2,114 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 stack, 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…