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/run)<a href="https://agentmods.dev/commands/madappgang/magus/run"><img src="https://agentmods.dev/badge/commands/madappgang/magus/run.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.00038 | $0.00743 |
| Opus 5 | $0.00019 | $0.00371 |
| Sonnet 5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
run scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
/terminal:run "curl -s https://api.example.com/health | jq" How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/terminal:run
Run a command in an isolated headless terminal, capture its output, and automatically clean up the session. This is the primary command for most terminal tasks.
Usage
/terminal:run {command}
Examples
/terminal:run npm test
/terminal:run bun test src/auth/
/terminal:run go test ./... -v
/terminal:run python3 -m pytest tests/
/terminal:run docker-compose up --build
/terminal:run "curl -s https://api.example.com/health | jq"
What It Does
- Executes the given command in an isolated headless session
- Captures the full output (no line limit — uses tee + file internally)
- Reports the results including exit code
- Auto-cleans the session on completion
The user never needs to manage session IDs or lifecycle.
When to Use /terminal:run vs Bash
| Scenario | Use |
|---|---|
| Simple non-interactive command | Bash tool |
| Command with colored/formatted output | /terminal:run |
| Command with interactive prompts | /terminal:run |
| TUI-rendered output (progress bars, tables) | /terminal:run |
| Commands needing a real TTY | /terminal:run |
| Long-running continuous process | /terminal:watch instead |
| Multi-step REPL session | /terminal:repl instead |
Behavior
For all one-shot commands
mcp__tmux__execute-command({ command: "<user_command>", headless: true })
Returns { output, exitCode } synchronously. Session is auto-destroyed. No session management needed.
For commands with complex output or streaming status
mcp__tmux__start-and-watch({
command: "<user_command>",
pattern: "\\$",
triggers: "exit,error",
mode: "medium",
headless: true,
timeout: 120
})
Use WatchResult.output for the results and WatchResult.event to distinguish success from error.
execute-command returns full output — no line limit since it captures via tee to a temp file rather than a fixed-size viewport.
Error Handling
- If the command hangs, use
mcp__tmux__pane-stateto check if it is waiting for input - If
WatchResult.event == "timeout", the command did not complete within the timeout — report and kill the session - For stuck processes, send
C-cviamcp__tmux__send-keyswithliteral: false
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 · 88 lines · 38 tokens per session scan A f5a3aa9cd115
run is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 743 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other commands, from other repositories
test-pr-docker
Test PR with Docker image build workflow.
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.
vios-sqa
VIOS SQA agent — build containers, deploy, run BDD tests, and validate web UI.
test
Execute the test suite for Golden Armada agents.
test
Generate integration tests for Alfresco extensions using Testcontainers (self-contained, no pre-running ACS required).