Borrowing it
Nothing to install: this file belongs to timvw/wt. 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/timvw/wt/main/AGENTS.mdgit clone --depth 1 https://github.com/timvw/wtWrote 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/timvw/wt/agents-md)<a href="https://agentmods.dev/instructions/timvw/wt/agents-md"><img src="https://agentmods.dev/badge/instructions/timvw/wt/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/timvw/wt/agents-md"><img src="https://agentmods.dev/badge/instructions/timvw/wt/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.02193 | $0.02193 |
| Opus 5.5 | $0.00877 | $0.00877 |
| Sonnet 5.5 | $0.00439 | $0.00439 |
| Haiku 4.5 | $0.00219 | $0.00219 |
Grade A, and why
wt 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 1mo 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines for AI Coding Agents
This document provides guidelines for AI coding agents (like Claude Code, Cursor, GitHub Copilot, etc.) working on the wt project.
Golden Rule: Use Worktrees!
IMPORTANT: As an AI agent, you should practice what this tool preaches - use worktrees for your work!
❌ DON'T: Switch branches in the main repository
# BAD - Don't do this!
cd /path/to/main/wt/repo
git checkout -b feature/new-branch
This leaves the user's main working directory on a feature branch.
✅ DO: Create worktrees for each task
# GOOD - Use wt to create isolated worktrees!
wt create feature/new-branch
# This creates: ~/dev/worktrees/wt/feature/new-branch
# Main repo stays on main branch
Agent Workflow
1. Starting New Work
When beginning a new feature or fix:
# Create a worktree for your feature
wt create feat/your-feature-name
# The worktree is automatically checked out to:
# ~/dev/worktrees/wt/feat/your-feature-name
2. Working in the Worktree
All file operations (Read, Write, Edit) should use paths in the worktree:
# Work in the worktree location
/Users/username/dev/worktrees/wt/feat/your-feature-name/
# NOT in the main repo:
# /Users/username/src/github/wt/ ❌
3. Committing and Creating PRs
# From within the worktree directory
git add .
git commit -m "feat: your feature description"
git push -u origin feat/your-feature-name
# Create PR
gh pr create --title "feat: your feature" --body "Description"
4. Cleaning Up
After the PR is merged:
# Remove the worktree
wt remove feat/your-feature-name
# or use the short alias:
wt rm feat/your-feature-name
Why This Matters for Agents
Benefits of Worktree-based Workflow
- Non-disruptive: User's main repository stays on
mainbranch - Isolated: Each feature gets its own directory
- Parallel work: Can work on multiple features simultaneously
- Clean state: No branch switching confusion
- Predictable: Always know where files are located
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.
- 1mo ago First seen · 321 lines · 2,193 tokens per session scan A b06c3c515437
wt AGENTS.md is an instructions file published in the GitHub repository timvw/wt (61 stars, last pushed 7d ago), licensed MIT. It adds 2,193 tokens to every session, about $0.0088 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-09-01.
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.