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.
git clone --depth 1 https://github.com/MadAppGang/magusWrote 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/commands/madappgang/magus/send)<a href="https://agentmods.dev/commands/madappgang/magus/send"><img src="https://agentmods.dev/badge/commands/madappgang/magus/send/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.
<a href="https://agentmods.dev/commands/madappgang/magus/send"><img src="https://agentmods.dev/badge/commands/madappgang/magus/send.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00982 |
| Opus 5.5 | $0.00018 | $0.00393 |
| Sonnet 5.5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
send 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/terminal:send
Advanced command — for most tasks, use
/terminal:run(one-shot commands),/terminal:repl(database and REPL queries), or/terminal:tui(TUI navigation) instead. Use this command only to send raw keystrokes by hand.
Types text or a named key into a slot, then captures the pane to show what happened.
Usage
/terminal:send [slot] {text}
/terminal:send [slot] key:{Name}
slot defaults to 1, the visible helper pane beside the user. Slot 1 is never the user's own pane.
send-keys Parameter Reference
mcp__plugin_terminal_mux__send-keys({ slot: 1, keys: "...", literal: true, enter: false })
literal: true (default) text is typed byte for byte; nothing is interpreted
literal: false keys is a named key from the vocabulary below
enter: true press Enter after the text (one call, not two)
send-keys is a creating tool: if the slot is not open yet, it opens it and returns created: true.
mcp__plugin_terminal_mux__send-keys({ slot: 1, keys: "bun test --watch", enter: true })
→ { "slot": 1, "created": true }
How to Use
Send plain text
/terminal:send ls -la src/
/terminal:send 2 SELECT count(*) FROM users LIMIT 1;
Sent with literal: true. Enter is not added; use key:Enter or enter: true.
Send a named key
key: maps to literal: false:
/terminal:send key:Enter
/terminal:send 2 key:Escape
/terminal:send 2 key:C-c
Run a command (text, then Enter)
/terminal:send "bun test --watch"
/terminal:send key:Enter
Or one call: mcp__plugin_terminal_mux__send-keys({ slot: 1, keys: "bun test --watch", enter: true }).
Named Key Vocabulary
These are the names the contract guarantees with literal: false. Anything else passes through to the tmux backend unmapped and is not portable.
| Key | Name |
|---|---|
| Enter, Escape, Tab, Space, Backspace | Enter, Escape, Tab, Space, BSpace |
| Arrows | Up, Down, Left, Right |
| Paging | PageUp, PageDown, Home, End |
| Function keys | F1 through F12 |
| Ctrl + x | C-x (for example C-c, C-d, C-l) |
| Alt + x | M-x |
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.
- 1mo ago Changed · -36 lines · +30 tokens per session 2d542f7819cc
- 1mo ago First seen · 147 lines · 14 tokens per session scan A fd6ed32f1ecc
send is a command published in the GitHub repository MadAppGang/magus (13 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 982 once invoked, about $0.0002 per session on Opus 5.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-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.