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/snapshot)<a href="https://agentmods.dev/commands/madappgang/magus/snapshot"><img src="https://agentmods.dev/badge/commands/madappgang/magus/snapshot.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.00016 | $0.00579 |
| Opus 5 | $0.00008 | $0.00290 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
snapshot 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/terminal:snapshot
Advanced command — For most tasks, use
/terminal:observeinstead. It lists sessions and takes snapshots automatically. Use this command only when you need raw pane capture access.
Read the current screen content of an active tmux pane.
Usage
/terminal:snapshot
/terminal:snapshot {paneId}
Pane IDs use the format %N (e.g., %3) or headless:%N (e.g., headless:%0).
What It Does
Takes a capture-pane of an active tmux pane and returns the current content as text — exactly what a human would see looking at that terminal.
All sessions are tmux panes. capture-pane returns pane content with optional scrollback via the lines parameter.
How to Use
Snapshot a specific pane
If you know the pane ID:
/terminal:snapshot %3
/terminal:snapshot headless:%0
Snapshot with scrollback
To get more than the visible viewport:
mcp__tmux__capture-pane({ paneId: "%3", lines: 200 })
Returns the last 200 lines of scrollback history plus the current viewport.
Snapshot without a known ID (list first)
If you don't know the pane ID, the command will list available sessions first:
/terminal:snapshot
This will:
- Call
mcp__tmux__list-sessionsto show all tmux sessions - Call
mcp__tmux__list-panesto enumerate panes - Capture the most relevant pane
Examples
See what's running in a server pane:
After starting a dev server with /terminal:watch, use /terminal:snapshot %3 to check current log output.
Debug a TUI application: If you started vim, htop, or lazygit in a headless session, use snapshot to see the current screen state.
Monitor test results: While a test watcher is running, snapshot the pane periodically to see updated results.
Notes
capture-panehas access to tmux scrollback history — uselines: Nto read more than the visible viewport.- For output longer than the visible pane, use
lines: 200or pipe command output to a temp file andReadit. - For persistent monitoring that waits for changes, use
/terminal:observe {paneId} --watchinstead.
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.
- 3d ago First seen · 78 lines · 16 tokens per session scan A 45335aa74ef6
snapshot is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 579 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.