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 agents/longbkit/clisbot/commandsgit clone --depth 1 https://github.com/longbkit/clisbotWhat 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.00000 | $0.01375 |
| Opus 5 | $0.00000 | $0.00687 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
commands 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Commands
Purpose
This document defines agent-scoped command dispatch inside a conversation.
It covers slash-prefixed commands and configurable shorthand command forms that are interpreted before a prompt is sent to the runner.
Boundary Rule
Agent command dispatch belongs to agents.
Why:
- it decides whether inbound text is treated as agent control or normal agent input
- it is scoped to one conversation session key inside an agent
- it must remain meaningful even if the concrete runner changes
It does not belong to runners, because runners should receive already-decided input.
It does not belong to control, because these commands are used inside a user conversation rather than an operator-only surface.
Dispatch Rule
When a message starts with /:
- check whether it matches a reserved control slash command
- if it matches, execute the control command immediately
- if it matches an agent-reserved execution command, execute that command
- otherwise, forward the slash command unchanged to the agent as native runner input
Control slash commands always have higher priority than native agent slash commands.
When a message starts with a configured bash shortcut such as !:
- treat the remaining text as an agent-scoped bash command
- execute it in the current agent workspace
Current Control Slash Commands
/start: show onboarding help for the current surface/help: show the available control slash commands/status: show the current route status and operator setup hints/whoami: return the current platform sender and route identity plus the current session id view for the active conversation/transcript: return the current full conversation session transcript/stop: sendEscapeto interrupt current processing in the current conversation session, clear clisbot's active-run state, and let queued prompts continue/new: start a new session for the current routed conversation and save the newsessionId/nudge: send one extraEnterto the current tmux session without resending the prompt body/queue <message>or\q <message>: create one durable queued prompt for the current session; attachments sent with the command stay attached to the queued prompt/queue list: show pending queued prompts for the current session/queue clear: clear pending queued prompts for the current session without interrupting a running prompt/followup status/followup auto/followup mention-onlyor/mention/followup mention-only channelor/mention channel/followup mention-only allor/mention all/followup pauseor/pause/followup resumeor/resume
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.
- 2d ago First seen · 148 lines · 0 tokens per session scan A f31b6115402a
commands is an agent published in the GitHub repository longbkit/clisbot (114 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,375 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.
Other agents, from other repositories
response-agent
Sen ResponseAgent'sın. Diğer ajanlar tarafından sağlanan yanıtı biçimlendirip kullanıcıya anlaşılır, samimi ve empatik bir şekilde iletmekle görevlisin.
planning-agent
Sen bir planlama ajanısın. Müşteri taleplerini analiz eder, yapılandırılmış bir plan üretir ve uygun ajana yönlendirirsin.
complaint-agent
Sen ComplaintAgent'sın. Şikayetleri complaintregistrationtool ile kaydedersin.
human-handoff-agent
Sen HumanHandoffAgent'sın. Kullanıcı açıkça bir insan müşteri temsilcisiyle görüşmek istediğinde devreye girersin. Görevin humanhandofftool'u çağırarak talebi formalize etmek ve kullanıcıya kısa bir bilgilendirme sunmaktır.
order-inquiry-agent
Sen OrderInquiryAgent'sın. Sipariş sorgularını işlersin.
order-placement-agent
Sen OrderPlacementAgent'sın. Siparişleri orderplacementtool ile oluşturursun.