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/braunmar/worktree/agents-mdgit clone --depth 1 https://github.com/braunmar/worktreeWhat 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.04526 | $0.04526 |
| Opus 5 | $0.02263 | $0.02263 |
| Sonnet 5 | $0.00905 | $0.00905 |
| Haiku 4.5 | $0.00453 | $0.00453 |
Grade A, and why
worktree 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 yesterday.
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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI coding agent when working with code in this repository.
Project Overview
Worktree Manager is a Go CLI tool for managing git worktrees in multi-instance development environments. It creates coordinated worktrees across multiple projects (backend, frontend), allocates ports dynamically, manages Docker instances, and integrates with Claude Code for autonomous development workflows.
Core Architecture
Registry System
Location: pkg/registry/registry.go
The registry is the source of truth for all worktree instances and port allocations:
- File:
worktrees/.registry.json - Structure: Maps normalized feature names to worktree metadata (branch, ports, projects, compose names)
- Port Allocation: Thread-safe allocation from configured ranges
- Persistence: Atomic writes with temp file + rename
Key Functions:
Load()- Loads registry from disk, builds port ranges from configAllocatePorts()- Finds available ports across all configured servicesFindAvailablePort()- Checks registry + live port availability (binds to verify)NormalizeBranchName()- Convertsfeature/user-auth→feature-user-auth
Configuration System
Location: pkg/config/workconfig.go
Configuration is loaded from .worktree.yml in the project root:
Key Structures:
WorktreeConfig- Main configuration (projects, presets, ports, symlinks, copies)ProjectConfig- Per-project settings (dir, main_branch, start_command, post_command)PresetConfig- Groups of projects (e.g., "fullstack" = backend + frontend)PortConfig- Port/service configuration (name, URL template, port expression, env var)
Port Expression Syntax:
Port values support dynamic calculation using {instance} placeholder:
- Simple offset:
"3000 + {instance}"→ 3000, 3001, 3002, ... - Multiplication:
"4510 + {instance} * 50"→ 4510, 4560, 4610, ... - Static value:
"8080"→ always 8080
Expression Parsing (parseExpression(), CalculatePort()):
- Replace
{instance}with actual instance number - Parse expression: base, offset, multiplier
- Calculate:
base + (offset * multiplier)orbase + offsetor justbase - Validate result is in range 1-65535
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.
- yesterday First seen · 514 lines · 4,526 tokens per session scan A 4bcd3edfacf7
worktree AGENTS.md is an instructions file published in the GitHub repository braunmar/worktree (5 stars, last pushed 6d ago), licensed MIT. It adds 4,526 tokens to every session, about $0.0226 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-31.
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.