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 agentmods add instructions/rohoswagger/ez-stack/agents-mdgit clone --depth 1 https://github.com/rohoswagger/ez-stackWhat 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 | $0.01103 | $0.01103 |
| Opus 5 | $0.00551 | $0.00551 |
| Sonnet 5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
ez-stack AGENTS.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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working with ez-stack.
Purpose
ez is a CLI for managing stacked pull requests on GitHub. If a repository has .git/ez/stack.json, branch management and PR operations should go through ez, not raw git checkout -b, git commit, git push, or gh pr create.
Install or update the tool
# First install
pip install ez-stack
ez setup --yes # configures shell integration (PATH + worktree auto-cd)
# Update to latest (auto-detects install method)
ez update
# Check for updates without installing
ez update --check
Requirements:
gitgh, authenticated viagh auth login- Rust/Cargo available to install
ez-stack
Install the skill
Install the ez-workflow skill for the current user so all agents auto-discover it:
ez skill install
# Installs canonical skill to ~/.agents/skills/ez-workflow/SKILL.md
# Symlinks agent-specific skill roots like ~/.claude/skills/ and ~/.codex/skills/
# Works from any directory
This installs the workflow defined in SKILL.md.
Core rule
When .git/ez/stack.json exists, prefer these commands:
- Create branch:
ez create <name> - Commit specific files:
ez commit -m "msg" -- path1 path2 - Commit all tracked changes:
ez commit -am "msg" - Commit tracked + untracked changes:
ez commit -Am "msg" - Commit patch-selected hunks:
git add -pthenez commit -m "msg" - Diff vs parent:
ez diff --statorez diff --name-only - Get parent branch:
ez parent - Push current branch and create/update PR:
ez push - Push the stack:
ez submit - Sync after trunk changes or merges:
ez syncorez sync --autostash - Repair a divergent GitHub native stack only when explicitly requested:
ez sync --repair-native-stack - Adopt branches from GitHub PRs:
ez adoptorez adopt --pr 42 - Inspect state programmatically:
ez status --jsonandez log --json
Avoid these raw commands in an ez-managed repo:
git checkout -b ...→ez creategit commit -m ...→ez commit -mgit push→ez pushgh pr create→ez pushgit diff main...HEAD→ez diff
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.
- 2d ago First seen · 144 lines · 1,103 tokens per session scan A 5425188495c0
ez-stack AGENTS.md is an instructions file published in the GitHub repository rohoswagger/ez-stack (23 stars, last pushed 20d ago), licensed MIT. It adds 1,103 tokens to every session, about $0.0055 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.
Other instructions, from other repositories
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.