Borrowing it
Nothing to install: this file belongs to 2389-research/terminal-title. 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/2389-research/terminal-title/main/CLAUDE.mdgit clone --depth 1 https://github.com/2389-research/terminal-titleWrote 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/2389-research/terminal-title/claude-md)<a href="https://agentmods.dev/instructions/2389-research/terminal-title/claude-md"><img src="https://agentmods.dev/badge/instructions/2389-research/terminal-title/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.1 | $0.00591 | $0.00591 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
terminal-title CLAUDE.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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal Title Plugin
Overview
This plugin automatically updates the terminal title with emoji + project + topic context to provide visual cues when switching between terminal windows.
Skills Included
terminal-title
Auto-invoked skill that:
- Detects current project from working directory, git repo, or package.json
- Infers topic from conversation context
- Reads emoji from
$TERMINAL_TITLE_EMOJIenvironment variable (defaults to 🎉) - Updates terminal title via platform-specific shell script
- Detects topic changes throughout the conversation and updates title accordingly
Environment Variables
TERMINAL_TITLE_EMOJI-- emoji prefix for the title. User sets this in their shell profile to distinguish contexts (e.g. 💼 for work, 🎉 for personal). Defaults to 🎉 if not set.CLAUDE_CODE_DISABLE_TERMINAL_TITLE-- set to1to disable Claude Code's built-in terminal title updater. Required so it doesn't conflict with this plugin.
Title Format
$EMOJI ProjectName - Topic
Examples:
💼 OneOnOne - Firebase Config🎉 dotfiles - zsh config
Hook Configuration
The plugin includes a session start hook:
{
"hooks": {
"sessionStart": {
"skill": "terminal-title"
}
}
}
This ensures the terminal title is set automatically when Claude Code starts.
How It Works
Project Detection
Determines project name using Claude's understanding of context:
- Git repository name or remote URL
- package.json name field
- README.md first heading
- Working directory basename (fallback)
Topic Inference
Infers topic from:
- Current conversation context (what user is working on)
- Defaults to "Claude Code" at session start
Shell Scripts
Cross-platform scripts in skills/scripts/:
set_title.sh-- Unix/Linux/macOS (bash)set_title.ps1-- Windows (PowerShell)
Both read $TERMINAL_TITLE_EMOJI from the environment, sanitize inputs, and send terminal escape sequences.
Development Workflow
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 · 89 lines · 591 tokens per session scan A 1a037946d26d
terminal-title CLAUDE.md is an instructions file published in the GitHub repository 2389-research/terminal-title (2 stars, last pushed 2mo ago), licensed MIT. It adds 591 tokens to every session, about $0.0030 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
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.
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).
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).
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.
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.