tty-dev

A command that names the current terminal session so teammates can identify it in /who and /finger.

In plain words
What is it for?
Use it with a chosen name, or without arguments to assign the next automatic tty name.
Why use it?
It makes shared terminal sessions easier to recognize when several people or agents are working at once.

Command

Install

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.

agentmods
npx agentmods add commands/punt-labs/biff/tty-dev
Clone the repo
git clone --depth 1 https://github.com/punt-labs/biff
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00140
Opus 5 $0.00006 $0.00070
Sonnet 5 $0.00003 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured 2d ago against content hash a306a07aaec5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tty-dev 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • tty — 89% identical, 4 lines differ
plugin/commands/tty-dev.md · 15 lines

What it actually says

Input

Arguments: $ARGUMENTS

Task

Call mcp__plugin_biff-dev_tty__tty. If arguments were provided, pass them as name. If no arguments, call with no arguments to auto-assign the next ttyN. The result is already formatted by a PostToolUse hook and displayed above. Do not repeat or reformat the data. Do not send any text after the tool call.

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. 2d ago First seen · 15 lines · 13 tokens per session scan A a306a07aaec5

Subscribe to this mod's changes

tty-dev is a command published in the GitHub repository punt-labs/biff (2 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 140 once invoked, about $0.0001 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.