Tab Out is a Chrome extension that replaces the new-tab page with a local dashboard of open browser tabs, grouping them by domain and providing tools to close, find, duplicate-check, or save tabs. It is for people who keep many tabs open and want to manage them without an account or server.
Borrowing it
Nothing to install: this file belongs to zarazhangrui/tab-out. 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/zarazhangrui/tab-out/main/AGENTS.mdgit clone --depth 1 https://github.com/zarazhangrui/tab-outWrote 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/zarazhangrui/tab-out/agents-md)<a href="https://agentmods.dev/instructions/zarazhangrui/tab-out/agents-md"><img src="https://agentmods.dev/badge/instructions/zarazhangrui/tab-out/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.00980 | $0.00980 |
| Opus 5 | $0.00490 | $0.00490 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
tab-out 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md -- Tab Out: Setup & Onboarding Guide for Coding Agents
You're installing Tab Out for the user. Your job is not just to set it up -- it's to get them excited about using it.
Step 0 -- Introduce the product
Before doing anything technical, tell the user what they're about to get:
Tab Out replaces your new tab page with a clean dashboard of everything you have open, grouped by domain.
Here's what makes it great:
- See all your open tabs at a glance grouped by domain on a grid
- Homepages group pulls Gmail, X, LinkedIn, YouTube, GitHub homepages into one card for easy cleanup
- Close tabs with style satisfying swoosh sound + confetti burst
- Duplicate detection flags when you have the same page open twice
- Click any tab title to jump to it even across different Chrome windows
- Save for later bookmark individual tabs to a checklist before closing them
- 100% local no server, no accounts, no data sent anywhere
It's just a Chrome extension. Setup takes about 1 minute.
Step 1 -- Clone the repo
git clone https://github.com/zarazhangrui/tab-out.git
cd tab-out
Step 2 -- Install the Chrome extension
This is the one step that requires manual action from the user. Make it as easy as possible.
First, print the full path to the extension/ folder:
echo "Extension folder: $(cd extension && pwd)"
Then, copy the extension/ folder path to their clipboard:
- macOS:
cd extension && pwd | pbcopy && echo "Path copied to clipboard" - Linux:
cd extension && pwd | xclip -selection clipboard 2>/dev/null || echo "Path: $(pwd)" - Windows:
cd extension && echo %CD% | clip
Then, open the extensions page:
open "chrome://extensions"
Then, walk the user through it step by step:
I've copied the extension folder path to your clipboard. Now:
- You should see Chrome's extensions page. In the top-right corner, toggle on Developer mode (it's a switch).
- Once Developer mode is on, you'll see a button called "Load unpacked" appear in the top-left. Click it.
- A file picker will open. Press Cmd+Shift+G (Mac) or Ctrl+L (Windows/Linux) to open the "Go to folder" bar, then paste the path I copied (Cmd+V / Ctrl+V) and press Enter.
- Click "Select" or "Open" and the extension will install.
You should see "Tab Out" appear in your extensions list.
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 · 97 lines · 980 tokens per session scan A 9cafc6ceb971
tab-out AGENTS.md is an instructions file published in the GitHub repository zarazhangrui/tab-out (1,787 stars, last pushed 4mo ago), licensed MIT. It adds 980 tokens to every session, about $0.0049 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.