terminal-title

terminal-title is a skill for Claude Code, Codex from eric861129/SKILLS_All-in-one. It costs 70 tokens per session (1,070 once invoked), scanned A, original, MIT.

A terminal helper that changes the terminal window title to describe the high-level task currently being handled.

In plain words
What is it for?
Use it to label terminals for tasks such as frontend work, backend work, debugging, or authentication changes.
Why use it?
It makes multiple terminal windows easier to tell apart when working on different tasks or running several coding-agent sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/john/project:.

Good fit Use it to label terminals for tasks such as frontend work, backend work, debugging, or authentication changes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for terminal-title

README.md
[![agentmods](https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/claude-code-terminal-title/github.svg)](https://agentmods.dev/skills/eric861129/skills_all-in-one/claude-code-terminal-title)
Your own site
<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/claude-code-terminal-title"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/claude-code-terminal-title/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.

agentmods 80×15 button for terminal-title

Your own site · 80×15
<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/claude-code-terminal-title"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/claude-code-terminal-title.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,070 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01070
Opus 5 $0.00035 $0.00535
Sonnet 5 $0.00014 $0.00214
Haiku 4.5 $0.00007 $0.00107

Measured 9d ago against content hash 2296d372a8f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

terminal-title 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 9d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/set_title.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

public/SKILLS/Development & Code Tools/claude-code-terminal-title/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Terminal Title

Overview

Automatically sets descriptive terminal window titles based on the task Claude is working on. Essential for developers running multiple Claude Code instances who need to quickly identify which terminal is handling which task.

When to Use

Always trigger this skill:

  • At the start of every new Claude Code session (after receiving the first user prompt)
  • When switching to a substantially different task (e.g., from "API Integration" to "Database Migration")

Trigger on task switches like these:

  • Switching from frontend work to backend work
  • Moving from debugging to new feature development
  • Changing from one module/component to a completely different one
  • Starting work on a different part of the system (e.g., from auth to payments)

Do NOT trigger for:

  • Follow-up questions about the same task ("Can you add a comment to that function?")
  • Small refinements to current work ("Make it blue instead of red")
  • Debugging the same feature you just built
  • Clarifications ("What did you mean by X?")
  • Iterating on the same component or module
  • Mid-task status updates or progress checks

How It Works

  1. Extract Task Summary: Analyze the user's prompt to identify the high-level task
  2. Generate Title: Create a concise, descriptive title (max 40 characters)
  3. Set Title: Execute the scripts/set_title.sh script with the generated title
  4. No Confirmation Needed: This happens automatically in the background

Title Format Guidelines

Good titles:

  • "API Integration: Auth Flow"
  • "Fix: Login Bug"
  • "DB Migration: Users Table"
  • "Build: Dashboard UI"
  • "Refactor: Payment Module"

Displayed as (with automatic folder prefix):

  • my-project | API Integration: Auth Flow
  • my-project | Fix: Login Bug

Bad titles:

  • Too long: "Implementing the new authentication system with OAuth2.0 support" (exceeds 40 chars)
  • Too generic: "Working" or "Coding"
  • Too verbose: "The user wants me to help them with..."

Read the full file on GitHub · 137 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 9d ago First seen · 137 lines · 70 tokens per session scan A 2296d372a8f5

Subscribe to this mod's changes

terminal-title is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 1,070 once invoked, about $0.0003 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-09-03.