2026-04-04-multi-surface-bash-command-addressing

2026-04-04-multi-surface-bash-command-addressing is an agent for coding agents from longbkit/clisbot. It costs 0 tokens per session (243 once invoked), scanned A, original, MIT.

A planned design for addressing multiple shell command surfaces within one agent session. A shell surface is a reusable command-running environment.

In plain words
What is it for?
It helps define command syntax, map shell names or numbers to runner targets, and preserve the current default of one reusable shell per session.
Why use it?
It would make it clear whether a command uses the default shell, a named or numbered shell, or a new one-off shell.

Agent

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 agents/longbkit/clisbot/2026-04-04-multi-surface-bash-command-addressing
Clone the repo
git clone --depth 1 https://github.com/longbkit/clisbot

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 2026-04-04-multi-surface-bash-command-addressing

README.md
[![agentmods](https://agentmods.dev/badge/agents/longbkit/clisbot/2026-04-04-multi-surface-bash-command-addressing.svg)](https://agentmods.dev/agents/longbkit/clisbot/2026-04-04-multi-surface-bash-command-addressing)
Your own site
<a href="https://agentmods.dev/agents/longbkit/clisbot/2026-04-04-multi-surface-bash-command-addressing"><img src="https://agentmods.dev/badge/agents/longbkit/clisbot/2026-04-04-multi-surface-bash-command-addressing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 243 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.00000 $0.00243
Opus 5 $0.00000 $0.00121
Sonnet 5 $0.00000 $0.00049
Haiku 4.5 $0.00000 $0.00024

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

Security

Grade A, and why

2026-04-04-multi-surface-bash-command-addressing 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 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.

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.

docs/tasks/features/agents/2026-04-04-multi-surface-bash-command-addressing.md · 36 lines

What it actually says

Multi-Surface Bash Command Addressing

Goal

Extend agent-scoped bash commands beyond the one default reusable shell surface.

Why This Exists

The current model keeps one reusable bash window per agent session.

That is the right default for now, but later the command surface should support explicit routing such as:

  • !1:
  • !bash:
  • one-off shell execution when isolation is preferred
  • multiple named shell surfaces inside one agent session

Scope

  • define the user-facing command grammar for explicit shell-surface addressing
  • define how shell surface names or indices map to tmux runner targets
  • define when a command should reuse an existing shell versus create a one-off shell
  • keep runner-specific target resolution out of channel code

Out Of Scope

  • changing the current default single-shell behavior
  • generic operator attach or inspect workflows

Acceptance Criteria

  • the command grammar for default, indexed, named, and one-off shell execution is defined
  • the default behavior remains one reusable shell surface per agent session
  • the mapping between agent commands and runner shell surfaces is unambiguous
  • docs and tests explain how shell-surface routing should work
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. 4d ago First seen · 36 lines · 0 tokens per session scan A 42545fda7ad4

Subscribe to this mod's changes

2026-04-04-multi-surface-bash-command-addressing is an agent published in the GitHub repository longbkit/clisbot (114 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 243 tokens. 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.