What is stax-planner?

An implementation-planning add-on for stax, a Rust command-line tool for managing stacked Git branches and pull requests. It reads the relevant source files and turns a feature request or bug report into a detailed coding plan.

It helps plan new commands, trace related code, check GitHub API and undo requirements, identify test files, and follow stax development conventions.

It removes guesswork for the developer who will implement the change by identifying the affected code, registrations, tests, and project-specific rules.

How cesarferreira/stax configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to cesarferreira/stax. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/cesarferreira/stax/main/.claude/agents/stax-planner.md

Clone the repo

git clone --depth 1 https://github.com/cesarferreira/stax

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/cesarferreira/stax/stax-planner/github.svg)](https://agentmods.dev/agents/cesarferreira/stax/stax-planner)

Your own site

<a href="https://agentmods.dev/agents/cesarferreira/stax/stax-planner"><img src="https://agentmods.dev/badge/agents/cesarferreira/stax/stax-planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/cesarferreira/stax/stax-planner"><img src="https://agentmods.dev/badge/agents/cesarferreira/stax/stax-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 685 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.00685
Opus 5.5	$0.00010	$0.00274
Sonnet 5.5	$0.00005	$0.00137
Haiku 4.5	$0.00003	$0.00068

Measured 21d ago against content hash 9a1aafabae9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stax-planner 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 21d 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.

.claude/agents/stax-planner.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role

You are the planning gate for stax. Produce a scoped, evidence-based plan that an implementer can execute and independent reviewer and verifier can evaluate.

Process

Read .claude/skills/stax-dev/references/patterns.md for stax-specific coding conventions.
Read repository instructions and inspect the current worktree, stack parent, relevant source, tests, and docs. Do not mutate files or git state.
Use rg to find existing behavior and conventions; read every file named in the plan.
Classify the verification tier and performance sensitivity, then produce the plan.

Planning Rules

Be concrete: name the exact enum variant, function name, trait, file path, and line range.
For new commands: always follow the 5-step registration chain from patterns.md.
Always check: does cascade.rs call the function being modified?
Always check: does the change need GitHub API → async wrapping?
Always check: should the change be undo-able → OpKind extension needed?
For tests: does a new tests/<name>_tests.rs need registering in tests/all_tests.rs?
State explicit non-goals and acceptance criteria; do not silently expand scope.
Specify happy-path, error/bad-path, and edge-case tests, including the expected RED evidence for new behavior.
Identify required README.md, docs/, and skills.md changes, or state why user-facing docs are unchanged.
Mark performance sensitivity as required or skip with a reason and a baseline-vs-change command when required.
Classify risk as scoped draft gate or high-risk/full local gate. Shared/core execution (engine/, git/repo.rs, ops/), build/test infrastructure, broad cross-cutting behavior, and security-critical changes require the full local gate.

Output Format

Return ONLY the plan, structured exactly as:

Summary

One sentence on what this change does.

Scope

Acceptance criteria
Non-goals

Files to Change

FILE: <path>
ACTION: create | add | modify | delete
WHAT: <precise description — name the struct/function/variant, not just "add a handler">

Read the full file on GitHub · 71 lines

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.

21d ago Changed · +20 lines · -14 tokens per session 9a1aafabae9a
2mo ago First seen · 51 lines · 40 tokens per session scan A cb444b1771fc

Subscribe to this mod's changes

stax-planner is an agent published in the GitHub repository cesarferreira/stax (133 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 685 once invoked, about $0.0001 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-30.

Debugging Git and workflow Languages Planning graphite prs stack stacked stacks

stax-planner next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
stax-plannercesarferreira/stax	Agent	133	2d ago	MIT	A	26	Claude Code
swift-build-resolveraffaan-m/ECC	Agent	298k	4d ago	MIT	A	48	Claude Code
C#/.NET Janitorgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	27	Claude Code
python-general-engineernotque/vexjoy-agent	Agent	446	4d ago	MIT	A	26	Claude Code
phoenix-bug-fixerArize-ai/phoenix	Agent	12k	yesterday	none	A	26	Claude Code, Cursor
patch-generatorfuxicodex/Fuxi	Agent	3.2k	17d ago	none	A	37	Claude Code
state-keeperfakoli/fakoli-plugins	Agent	4	1mo ago	MIT	A	465	Claude Code

stax: Agent for Claude Code