stax: Instructions file for Claude Code

CLAUDE.md

stax CLAUDE.md is an instructions file for Claude Code from cesarferreira/stax. It costs 1,278 tokens per session, scanned A, original, MIT.

A set of development instructions for the stax Rust command-line project, including commands for building, testing, checking, formatting, installing, and running it. Rust is the programming language used by the project.

In plain words
What is it for?
It helps build debug or release versions, run scoped or full tests, check and lint code, format it, install the tool locally, and run commands.
Why use it?
It gives contributors a consistent way to work on the code and clarifies which test and quality checks are expected.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is cesarferreira/stax's own configuration. It tells Claude Code how to work on stax itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything stax configures →

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

agentmods badge for stax CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cesarferreira/stax/claude-md.svg)](https://agentmods.dev/instructions/cesarferreira/stax/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/cesarferreira/stax/claude-md"><img src="https://agentmods.dev/badge/instructions/cesarferreira/stax/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,278 This file is loaded in full into every session.
When invoked 1,278 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01278 $0.01278
Opus 5 $0.00639 $0.00639
Sonnet 5 $0.00256 $0.00256
Haiku 4.5 $0.00128 $0.00128

Measured 8d ago against content hash ea5a65e4d9d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

stax CLAUDE.md 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 8d 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.md · 101 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Development Commands

# Build debug version
cargo build

# Build release version
cargo build --release

# Run full test suite (preferred)
make test

# Run full suite natively on host (explicit override)
make test-native

# Run a single test (filter by name; scope a former file with a module prefix, e.g. status_tests::)
cargo nextest run test_name

# Check + lint (both required before commit)
cargo check && cargo clippy -- -D warnings

# Format code
cargo fmt

# Install locally
cargo install --path .

# Run with arguments
cargo run -- <command>

Test Runner Policy

  • Do not run the full suite via cargo test in this repo.
  • While iterating, scope runs to what changed: cargo nextest run test_name (or a module prefix, e.g. status_tests::) for the tests you added or touched.
  • Run make test once before considering work done, before opening a PR, or whenever a change touches shared/core logic (e.g. engine/, git/repo.rs) that many tests depend on — CI also runs the full suite, but catching a shared-code regression locally is cheaper than a post-push CI failure.
  • On macOS, this route intentionally uses Docker for speed and consistency.
  • All integration tests compile into ONE binary (tests/all_tests.rs; autotests = false in Cargo.toml) so cargo links a single test binary instead of ~50. When you add a new tests/<name>_tests.rs, you MUST register it in tests/all_tests.rs with #[path = "<name>_tests.rs"] mod <name>_tests;, and reach shared helpers via use crate::common; (not mod common;). cargo test --test <name> only accepts all_tests; scope runs by module path instead.

Architecture Overview

stax is a Rust CLI for managing stacked Git branches and PRs, compatible with freephite's metadata format.

Module Structure

  • src/main.rs - Binary entry point; delegates to stax::cli::run().
  • src/cli.rs - CLI definition using clap derive macros. Defines Commands enum with all subcommands, their flags, and the dispatch logic.
  • src/commands/ - Command implementations. Each file corresponds to a CLI command (status, submit, sync, restack, etc.).
  • worktree/ - stax worktree subcommands: create, list, go, remove, cleanup, restack, ll
  • worktree/ai.rs - stax lane command: AI worktree lane shortcut (tmux-backed, agent launcher)
  • shell_setup.rs - stax setup (or st setup) for shell function installation
  • src/engine/ - Core domain logic:
    • metadata.rs - BranchMetadata struct stored per-branch (parent name, parent revision, PR info)
    • stack.rs - Stack struct that builds the full branch tree from metadata
  • src/git/ - Git operations:
    • repo.rs - GitRepo wrapper around git2 with rebase, checkout, merge operations; also hosts WorktreeInfo (pub), list_worktrees() (pub), worktree_create(), worktree_remove(), worktrees_dir(), main_repo_workdir()
    • refs.rs - Low-level ref operations for storing metadata in refs/branch-metadata/<branch>
  • src/github/ - GitHub API client using octocrab for PR creation/updates
  • src/config/mod.rs - User configuration (~/.config/stax/config.toml) and credential management

Read the full file on GitHub · 101 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.

  1. 8d ago First seen · 101 lines · 1,278 tokens per session scan A ea5a65e4d9d4

Subscribe to this mod's changes

stax CLAUDE.md is an instructions file published in the GitHub repository cesarferreira/stax (123 stars, last pushed today), licensed MIT. It adds 1,278 tokens to every session, about $0.0064 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-30.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens