Borrowing it
Nothing to install: this file belongs to webteractive/zetty. 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/webteractive/zetty/main/AGENTS.mdgit clone --depth 1 https://github.com/webteractive/zettyWrote 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/webteractive/zetty/agents-md)<a href="https://agentmods.dev/instructions/webteractive/zetty/agents-md"><img src="https://agentmods.dev/badge/instructions/webteractive/zetty/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/webteractive/zetty/agents-md"><img src="https://agentmods.dev/badge/instructions/webteractive/zetty/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.03904 | $0.03904 |
| Opus 5.5 | $0.01562 | $0.01562 |
| Sonnet 5.5 | $0.00781 | $0.00781 |
| Haiku 4.5 | $0.00390 | $0.00390 |
Grade A, and why
zetty 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- zetty CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zetty — Agent & Contributor Guide
Guidance for AI agents and contributors working in this repo.
CLAUDE.mdandAGENTS.mdare kept byte-identical — edit one and mirror the change to the other in the same commit (see Conventions).
What this is
Zetty is a native macOS (Linux later) GUI terminal multiplexer built on
full libghostty (via the prebuilt libghostty-spm package) with a Swift
AppKit application layer. Work is organized around pinnable projects, each
owning tabs and nested split panes. See README.md.
Layout
Sources/ZettyCore/**— pure, testable model (no AppKit):Surface,SurfaceNode,PaneTree,TabList,WorkspaceModel, persistence.App/Sources/App/**— AppKit app:AppDelegate,TerminalViewController,SidebarView,TabBarView,SurfaceNodeView,PaneActions,Theme.swift.App/Sources/ZettyGhostty/**— libghostty bridge:SurfaceRegistry,Ghostty.
Build / run
The Xcode project is Tuist-generated. Project.swift declares sources as
globs (App/Sources/App/**), but the generated .xcodeproj enumerates the
resolved file list — so after adding or removing a file you must regenerate.
You do not edit Project.swift to register a new file; only new targets,
resources, or settings need a manifest change. Files under Sources/ZettyCore/
need nothing at all for swift test (SwiftPM globs them at build time).
mise exec -- tuist generate --no-open
xcodebuild -project zetty.xcodeproj -scheme zetty -destination 'generic/platform=macOS' build
Tests: mise exec -- tuist test runs the app test target. The pure ZettyCore
suite is faster via SwiftPM — mise exec -- swift test — and a single test with
--filter, e.g. mise exec -- swift test --filter moveProjectRejectsCrossGroupMove.
Every change ← always applies; the details are in the rules named
- Before starting any feature, fix or other change, run
scripts/check-libghostty.sh(once per working session) and state the result in the summary: "libghostty is current", or what is newer, plus where the bundled Ghostty commit stands against Ghostty's latest release (the script'sghostty in …line). Exit 2 means GitHub could not be reached, which is not "up to date". Anything newer: readlibghostty-bump.mdbefore touching the pin. - Verify before the commit in the isolated test app
(
isolated-test-app.md), never by quitting or replacing/Applications/zetty.app. - After the commit, install the new build and relaunch, without asking
(
install-after-change.md): build after committing,dittoin place, and confirm this session's surface is tracked beforezetty quit. - UI follows the design rules (
design-rules.md, visual spec inDESIGN.md): never hardcode a color; chrome usesZTheme.chromeFont, only the terminal and status bar the mono font. - Machine-driven chrome refreshes coalesce through
setNeedsChromeRefresh(chrome-refresh.md). - A new config key uses the
zetty-namespace and ships with a Settings control (configuration.md). - A new keyboard shortcut needs proof its chord is free on all four
shortcut surfaces (
keybindings-copy-mode.md). - Anything new that ships in the app needs its license in
THIRD_PARTY_NOTICES.mdandlicenses/, every libghostty bump included (third-party-notices.md). - Release only with
scripts/release.shand human-written notes (releasing.md): a generic release tool silently ships a broken release.
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 Changed · +2 lines · +30 tokens per session 0a13f93fcf04
- 9d ago Changed · -326 lines · -4,907 tokens per session scan C → A 399e92b3998a
- 11d ago Changed · +1 lines · +72 tokens per session 1c6619f157bf
- 12d ago Changed · +1 lines · +14 tokens per session 6858b84e532a
- 14d ago Changed · +5 lines · +22 tokens per session ed3f34ea589c
- 19d ago Changed · +7 lines · +126 tokens per session 060317c0fa5b
- 21d ago Changed · +1 lines · +125 tokens per session 2b8c583f2a49
- 22d ago Changed · +15 lines · +318 tokens per session 489f9f58ed7a
- 23d ago Changed · +11 lines · +213 tokens per session 1249694756df
- 26d ago First seen · 433 lines · 7,891 tokens per session scan C 27ae6eef212b
zetty AGENTS.md is an instructions file published in the GitHub repository webteractive/zetty (2 stars, last pushed yesterday), licensed MIT. It adds 3,904 tokens to every session, about $0.0156 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-31.
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.