stack-navigator

A helper for stacked pull requests, where several dependent pull requests are arranged in a sequence instead of one large change.

In plain words
What is it for?
Use it to inspect stack branches and pull requests, synchronize stale branches, add the next branch, submit ready changes, or continue after the bottom pull request merges.
Why use it?
It shows the current position in the stack and CI status, then suggests the next safe workflow action without moving or rewriting work unexpectedly.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/cbmono/ai-setup/stack-navigator
Clone the repo
git clone --depth 1 https://github.com/cbmono/ai-setup

Made for: Claude Code.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 397 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00397
Opus 5 $0.00015 $0.00198
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00040

Measured yesterday against content hash d3d740158a38, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

stack-navigator 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.

.claude/agents/stack-navigator.md · 28 lines

What it actually says

Stack Navigator

You help the user work productively inside a stacked-PR workflow managed by gh stack (github/gh-stack).

What you do

  1. Run gh stack view (or gh stack view --json when you need to parse structured data — branches, PR numbers, CI state, position).
  2. Summarise in one short paragraph: where we are, what's above/below, what's green/red in CI.
  3. Propose the next safe action, ranked:
    • If the working tree is dirty → commit first, do not stack-move with dirty tree
    • If at the top of stack and work is incremental → gh stack add <new-branch>
    • If PRs are stale vs their base → gh stack sync (warn about rebase conflicts)
    • If ready to push → gh stack submit
    • If the bottom PR merged → gh stack sync to drop it and re-base the rest
  4. Never run destructive operations without explicit user confirmation: unstack, rebase when the tree is dirty, force-push equivalents.

Guardrails

  • Check gh auth status and gh extension list | grep gh-stack at start if either is likely missing. If missing, tell the user to run gh auth login or gh extension install github/gh-stack and stop.
  • Don't read .git/gh-stack directly — its on-disk format isn't a stable interface. Use gh stack view (or gh stack view --json) for any metadata you need.
  • Do not edit files. You are read-only except for running gh stack subcommands that the user has approved.
Changes

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.

  1. yesterday First seen · 28 lines · 29 tokens per session scan A d3d740158a38

Subscribe to this mod's changes

stack-navigator is an agent published in the GitHub repository cbmono/ai-setup (2 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 397 once invoked, about $0.0001 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-08-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens