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.svg" alt="Measured on agentmods" 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.00014 | $0.01158 |
| Opus 5 | $0.00007 | $0.00579 |
| Sonnet 5 | $0.00003 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
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 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 — 147 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/REPL queries), or/terminal:tui(TUI navigation) instead. Use this command only when you need to send raw keystrokes manually.
Send keystrokes or text input to an active terminal pane and see the result.
Usage
/terminal:send {paneId} {text or keys}
/terminal:send {paneId} key:{KeyName}
Pane IDs use the format %N (e.g., %3) or headless:%N (e.g., headless:%0).
send-keys Parameter Reference
mcp__tmux__send-keys({ paneId: "%66", keys: "...", literal: ? })
literal: true (default) — text is sent byte-for-byte; special characters are NOT
interpreted as key sequences. Use for typing commands.
literal: false — text is interpreted as tmux key names. Use for:
- Control sequences: "C-c", "C-d", "Escape", "Enter"
- Arrow keys: "Up", "Down", "Left", "Right"
- Function keys: "F1" through "F12"
To type text AND execute (press Enter):
mcp__tmux__send-keys({ paneId, keys: "bun test --watch", literal: true })
mcp__tmux__send-keys({ paneId, keys: "Enter", literal: false })
What It Does
Injects text or named keystrokes into an active terminal pane, then takes a capture-pane snapshot to show the result.
How to Use
Send plain text
Send a command or text string to be typed in the terminal:
/terminal:send %3 ls -la src/
/terminal:send headless:%0 SELECT count(*) FROM users LIMIT 1;
The text will be sent as-is with literal: true — it does NOT automatically add Enter at the end.
Send named keys
Use key: prefix for special keys (sent with literal: false):
/terminal:send %3 key:Enter
/terminal:send %3 key:Escape
/terminal:send %3 key:Tab
/terminal:send %3 key:C-c
Send text + Enter (run a command)
To send text and execute it — two separate calls:
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 · 147 lines · 14 tokens per session scan A fd6ed32f1ecc
send is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,158 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.