Borrowing it
Nothing to install: this file belongs to aasimsani/gwt-zsh. 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/aasimsani/gwt-zsh/main/AGENTS.mdgit clone --depth 1 https://github.com/aasimsani/gwt-zshWrote 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/aasimsani/gwt-zsh/agents-md)<a href="https://agentmods.dev/instructions/aasimsani/gwt-zsh/agents-md"><img src="https://agentmods.dev/badge/instructions/aasimsani/gwt-zsh/agents-md.svg" alt="Measured on agentmods" 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.01520 | $0.01520 |
| Opus 5 | $0.00760 | $0.00760 |
| Sonnet 5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
gwt-zsh 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 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
gwt-zsh — Stupidly simple git worktree management for Zsh.
What This Project Is
A Zsh plugin (gwt.plugin.zsh, ~1250 lines) that wraps git worktree with smart naming, stacking, navigation, and interactive pruning. Single-file plugin, no external dependencies beyond git (fzf optional for better UI).
Repository: aasimsani/gwt-zsh | License: MIT | Language: Zsh
Command Reference
| Command | Shorthand | Description |
|---|---|---|
gwt <branch> |
Create worktree from main branch, cd into it | |
gwt --stack <branch> |
gwt -s |
Create worktree branched from current branch (tracks parent) |
gwt --from <base> <branch> |
gwt -f |
Create worktree from a specific base branch |
gwt --base |
gwt .. |
Navigate to parent worktree |
gwt --root |
gwt ... |
Navigate to main worktree (ultimate root) |
gwt --info |
gwt -i |
Show current worktree's stack relationships |
gwt --list |
List all worktrees with hierarchy indicators | |
gwt --prune |
Interactive multi-select worktree cleanup | |
gwt --config |
Configure directories to auto-copy to new worktrees | |
gwt --copy-config-dirs <dir> |
Copy specific directory when creating worktree | |
gwt --list-copy-dirs |
List configured copy directories | |
gwt --version |
Show version | |
gwt --update |
Self-update from GitHub | |
gwt --help |
gwt -h |
Show help |
Naming Convention
Worktrees are created as sibling directories with auto-generated names:
- Linear ticket branches (
*/eng-XXXX-*): extracts ticket number →../repo-eng-1045 - Regular branches: first 3 words of branch name →
../repo-add-new-dashboard - If worktree already exists,
gwtjust cd's into it.
Architecture
File Structure
gwt.plugin.zsh # Entire plugin (single file)
tests/gwt.zunit # Test suite (zunit framework)
scripts/
release.zsh # Automated release script
coverage_check.zsh # Coverage validation
.githooks/ # Pre-commit hook (runs tests)
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.
- 8d ago First seen · 141 lines · 1,520 tokens per session scan A 9ea3bbd577ec
gwt-zsh AGENTS.md is an instructions file published in the GitHub repository aasimsani/gwt-zsh (11 stars, last pushed 3mo ago), licensed MIT. It adds 1,520 tokens to every session, about $0.0076 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
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.
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.
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 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).
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.