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/session)<a href="https://agentmods.dev/commands/madappgang/magus/session"><img src="https://agentmods.dev/badge/commands/madappgang/magus/session.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.00019 | $0.00959 |
| Opus 5 | $0.00010 | $0.00479 |
| Sonnet 5 | $0.00004 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
session 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/terminal:session
Advanced command — For most tasks, use
/terminal:run,/terminal:watch, or/terminal:replinstead. They handle session lifecycle automatically. Use this command only when you need manual control over sessions.
Create, list, and manage terminal sessions using tmux-mcp.
Usage
/terminal:session list
/terminal:session tmux list
/terminal:session tmux create {name}
/terminal:session headless create
/terminal:session headless close {paneId}
/terminal:session headless close-all
Subcommands
list — Show all active sessions
/terminal:session list
Lists all active tmux sessions (both regular and headless) with their pane IDs and metadata.
Use this to:
- Find a pane ID when you've forgotten it
- Check for orphaned headless sessions to clean up
- Verify a session was closed successfully
tmux list — List tmux sessions
/terminal:session tmux list
Lists all active tmux sessions with their windows and panes. This shows the developer's existing tmux environment — do not kill these sessions.
tmux create — Create a tmux session
/terminal:session tmux create myproject
Creates a new named tmux session. tmux sessions are visible to the user and can be attached to from their terminal.
headless create — Create a headless session
/terminal:session headless create
Creates an isolated headless session for running a command invisibly.
mcp__tmux__create-headless({ name: "my-task" }) → { paneId: "headless:%0" }
headless close — Close a headless session
/terminal:session headless close headless:%0
Kills a specific headless session and releases its resources.
mcp__tmux__kill-session({ sessionId: "headless:$0" })
Always close sessions when you are done with them.
headless close-all — Close all headless sessions
/terminal:session headless close-all
Terminates all headless sessions at once.
mcp__tmux__kill-headless-server()
Useful for bulk cleanup after a long workflow.
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 · 145 lines · 19 tokens per session scan A 82cd109e697d
session is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 959 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.