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 ronaknnathani/relay --skill stack-shipgit clone --depth 1 https://github.com/ronaknnathani/relayWrote 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/ronaknnathani/relay/stack-ship)<a href="https://agentmods.dev/skills/ronaknnathani/relay/stack-ship"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/stack-ship/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/ronaknnathani/relay/stack-ship"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/stack-ship.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.00060 | $0.02530 |
| Opus 5.5 | $0.00024 | $0.01012 |
| Sonnet 5.5 | $0.00012 | $0.00506 |
| Haiku 4.5 | $0.00006 | $0.00253 |
Grade A, and why
stack-ship 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Ship
Drive a design or feature goal from intake to "all PRs merged" with near-zero steering. The orchestrator is a router, not a worker: it owns the plan, state, delegation, and author-facing decisions; subagents own execution and return structured digests.
The guardrails are non-negotiable — read them before acting.
Throughout this skill
masterdenotes the repository's default branch; substitute the real default (main, etc.). Auto-merge is armed only on a default-branch-based PR — which, in a stack, is exactly the front PR.
The one-paragraph model
You (orchestrator) turn a goal into an acceptance-criteria list and a stacked PR plan
(api → utils → stitch, smallest single-intent PRs). You spawn a deliver-pr sub-agent per PR to
run the full single-PR pipeline and open the PR. You drive whichever PR currently sits on master (the
front of the stack) to merged by pointing the relay pr watch runtime at it with yourself as the
owner and running pr-monitor once for each digest it wakes you with, and you add only the
stack-specific front-advance and cascade. You never write code, never post in your own voice, never
approve, never make author-owned design decisions, and never install unreviewed tooling — you route
work and surface questions. You stop when every acceptance criterion is met and every PR is merged.
When to use / not use
- Use for a multi-PR feature with a clear goal and a discoverable current→desired delta.
- Use again / resume for an active stacked delivery run. On resume, reconstruct state, make sure exactly one watcher is running for the current front project, and handle any digest it already recorded — the author should not have to type a special "monitor-tick mode" prompt.
- Don't use for a single small change (just do it), or when the goal/delta is too vague to write
acceptance criteria — first run
brainstorming/ ask the author to sharpen the goal.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +12 lines · -37 tokens per session e6106595c2a2
- 1mo ago First seen · 138 lines · 97 tokens per session scan A 67dd375e9a2e
stack-ship is a skill published in the GitHub repository ronaknnathani/relay (3 stars, last pushed 23d ago), licensed MIT. It adds 60 tokens to every session and 2,530 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Use when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example…
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
repo-status
Checks the status of the repository.
repo-status
Checks the status of the repository.
git-ops
Safe git operations including commits, branches, merges, worktrees, and conflict resolution. Use when user wants to commit and push changes, manage branches, resolve conflicts, or create isolated workspaces. Activates when user says "commit", "push", "merge", "branch", "pull", "rebase", "worktree", "conflict", or…