Borrowing it
Nothing to install: this file belongs to rohoswagger/ez-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rohoswagger/ez-stack/main/CLAUDE.mdgit clone --depth 1 https://github.com/rohoswagger/ez-stackWrote 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/instructions/rohoswagger/ez-stack/claude-md)<a href="https://agentmods.dev/instructions/rohoswagger/ez-stack/claude-md"><img src="https://agentmods.dev/badge/instructions/rohoswagger/ez-stack/claude-md/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/instructions/rohoswagger/ez-stack/claude-md"><img src="https://agentmods.dev/badge/instructions/rohoswagger/ez-stack/claude-md.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.05336 | $0.05336 |
| Opus 5.5 | $0.02134 | $0.02134 |
| Sonnet 5.5 | $0.01067 | $0.01067 |
| Haiku 4.5 | $0.00534 | $0.00534 |
Grade A, and why
ez-stack 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 2mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ez-stack — Project CLAUDE.md
This is a living document. Update it whenever the product mission evolves, a significant design decision is made, a pattern is established, or a new version ships. It is the source of truth for anyone (human or AI) working on this codebase.
Product Mission
ez-stack makes stacked PRs on GitHub effortless, primarily for AI coding agents.
Agents are the primary audience. Humans benefit too, but when there's a design tradeoff, optimize for agents. Every command should be simpler, more intuitive, and more efficient than the raw git/gh equivalent — the goal is to make version control easier for agents, not to expose git's complexity through a different interface.
Every feature should be inherently more useful than the git commands it replaces.
Core Design Principles
-
Shell out, don't reimplement.
ezorchestratesgitandgh. It doesn't reimplement git logic. When in doubt, run the real command. -
Auto-restack on every mutation. Any command that moves a branch tip (
commit,amend,move) automatically restacks children. Users should never have to think about rebasing. -
State is append-only metadata. Stack state lives in
.git/ez/stack.json— just branch names, parents, parent SHAs, and PR numbers. It is never the source of truth for git state; git is. -
Fail loudly with hints. Every error message tells the user what went wrong AND what to do next. No silent failures.
-
Human output on stderr, machine output on stdout. Colored tree output and spinners go to stderr. JSON output (
--json), URLs (ez pr-link), and anything meant to be piped goes to stdout. -
Structured exit codes. Agents branch on failure type. Exit codes are documented and stable:
- 0 = success
- 1 = unexpected error
- 2 = GitHub API /
ghCLI error - 3 = restack blocked — rebase conflict, or one or more branches skipped during a sync/restack (manual resolution required)
- 4 = stale remote ref
- 5 = usage error (on trunk, branch not tracked, etc.)
- 6 = unstaged 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.
- 2mo ago First seen · 217 lines · 5,336 tokens per session scan A 09c57ac2d4f4
ez-stack CLAUDE.md is an instructions file published in the GitHub repository rohoswagger/ez-stack (23 stars, last pushed 2mo ago), licensed MIT. It adds 5,336 tokens to every session, about $0.0213 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.