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/eiler2005/ai-tab-optimizer/claude-mdgit clone --depth 1 https://github.com/eiler2005/ai-tab-optimizerWrote 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/eiler2005/ai-tab-optimizer/claude-md)<a href="https://agentmods.dev/instructions/eiler2005/ai-tab-optimizer/claude-md"><img src="https://agentmods.dev/badge/instructions/eiler2005/ai-tab-optimizer/claude-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 | $0.01027 | $0.01027 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
ai-tab-optimizer CLAUDE.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
pnpm health # curl health check How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Tab Optimizer — Claude Code Guide
Full product spec: @PROJECT.md | Dev setup: @SETUP.md | Feature scope: @MVP_FEATURES.md
Core Rules
- No
any— useunknownwith type narrowing. - Typecheck after every change —
cd extension && pnpm typecheck. Stop on errors. - No speculative abstractions — don't create helpers unless there are 3+ call sites.
- No comments unless logic is non-obvious. Never restate what code already says.
- Follow existing patterns — Zustand actions, discriminated union messages, Tailwind classes,
@shared/*imports. - Update docs when feature behavior changes.
Commands
# Extension
cd extension && pnpm install # install deps
pnpm dev # watch mode → dist/
pnpm build # typecheck + vite build
pnpm typecheck # TS check only
# AI Server
pnpm server # FastAPI on localhost:8765
pnpm health # curl health check
# Load in Chrome
# chrome://extensions → Developer mode → Load unpacked → extension/dist/
# After service worker changes: click Reload on extension card
Workflow
Every non-trivial feature follows three phases — do not skip:
1. Research — /research <topic> — reads code, writes docs/research/<slug>.md
2. Plan — /plan <feature> — creates docs/plans/<slug>.md with task checklist. Do NOT code until approved.
3. Implement — /implement <path-to-plan> — executes tasks, typechecks, marks done.
For small changes (typo, rename, single-line fix): skip planning, implement directly.
Skills (.claude/skills/)
| Skill | Trigger | Purpose |
|---|---|---|
/research |
Manual | Deep-research a topic, output to docs/research/ |
/plan |
Manual | Create implementation plan in docs/plans/ |
/implement |
Manual | Execute an approved plan task by task |
Subagents (.claude/agents/)
| Agent | Model | Use case |
|---|---|---|
code-reviewer |
Sonnet | Review code for patterns, edge cases, project conventions |
security-reviewer |
Opus | Scan for injection, secrets, XSS, OWASP top 10 |
test-writer |
Sonnet | Generate Vitest / pytest tests for given files |
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.
- 4d ago First seen · 101 lines · 1,027 tokens per session scan A fa95eb970bef
ai-tab-optimizer CLAUDE.md is an instructions file published in the GitHub repository eiler2005/ai-tab-optimizer (3 stars, last pushed 3mo ago), licensed MIT. It adds 1,027 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
AIPex AGENTS.md
Instructions for AIPexStudio/AIPex, covering package architecture, building and running, writing tests, test structure and framework and mocking (vi from vitest).
rolemule CLAUDE.md
Claude Code instructions for eliornl/rolemule, covering rolemule — claude code rules index, rule files and non-negotiables (always true — no file needed).
llm-brain CLAUDE.md
Instructions for kimsanguine/llm-brain, covering llm-brain — claude code 운영 지침, 가드레일 (절대 위반 금지), 프라이버시 경계 (agent memory os), 명령어 and ingest.
AIPex CLAUDE.md
Instructions for AIPexStudio/AIPex, a project described as: AIPex: AI browser automation assistant, no migration and privacy first. Alternative to Manus Browser Operator、 Claude Chrome and Agent Browser.
geolens CLAUDE.md
Claude Code instructions for geolens-io/geolens: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
textbook-to-note CLAUDE.md
Instructions for drpwchen/textbook-to-note, covering claude.md — which audience are you?, working on this repo, spec before code, how much ceremony — decide before you start and the commit guard.