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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/rohoswagger/ez-stack/agents-md"><img src="https://agentmods.dev/badge/instructions/rohoswagger/ez-stack/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/rohoswagger/ez-stack/agents-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.01103 | $0.01103 |
| Opus 5.5 | $0.00441 | $0.00441 |
| Sonnet 5.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 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 — 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.
- 2mo 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 2mo ago), licensed MIT. It adds 1,103 tokens to every session, about $0.0044 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.