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/jayvee/aigonWrote 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/jayvee/aigon/sessions-close)<a href="https://agentmods.dev/commands/jayvee/aigon/sessions-close"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/sessions-close/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/jayvee/aigon/sessions-close"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/sessions-close.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.00014 | $0.00430 |
| Opus 5.5 | $0.00006 | $0.00172 |
| Sonnet 5.5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
sessions-close 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aigon-sessions-close — 94% identical, 14 lines differ
What it actually says
aigon-sessions-close
Kill all running agent processes for a given feature or research ID, and close the Warp Fleet tab.
Usage
/aigon:sessions-close <ID>
/aigon:sessions-close 05— close all agent sessions for research/feature #05/aigon:sessions-close 55— close all agent sessions for feature #55
When to Use
Use this after agents have completed their work (research findings or feature implementation) and you want to tear down the Fleet run quickly without typing exit in each pane.
What It Does
- Kills all running agent processes whose command line contains the ID (feature-do, feature-code-review, feature-review, research-do)
- Attempts to close the Warp Fleet tab/window via AppleScript (best-effort)
- Reports what was killed
Works for both feature Fleet runs (arena-feature-55) and research Fleet runs (arena-research-05).
Example
After agents have completed:
aigon sessions-close 55
Output:
Closing all agent sessions for #55...
✓ Killed: aigon:feature-do 55
✓ Killed: aigon:feature-do 55
✅ Warp Fleet tab closed.
Notes
- If no processes are running (agents already exited), it prints a notice and still tries to close the Warp tab
- Warp tab close is best-effort — if AppleScript can't find the window, you'll see a reminder to close it manually
- Works for any mix of agents (cc, ag, cx, cu)
Step 1: Run the CLI command
aigon sessions-close {{args}}
Step 2: Confirm to user
Tell the user:
- Which sessions were closed
- Whether the Warp tab was closed automatically
ARGUMENTS: {{args}}
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 First seen · 66 lines · 14 tokens per session scan A c6bc437ba432
sessions-close is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It adds 14 tokens to every session and 430 once invoked, about $0.0001 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-03.
Other commands, from other repositories
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
mach12:gh-issue-read
Read a GitHub issue's title, body, and all comments; optionally locate an HTML-marker comment.
mach12:gh-assign
Assign the current user to one or more GitHub issues, handling existing assignees.
mach12:gh-sub-issues
Detect sub-issues of a GitHub issue using the two-strategy approach (API, then body-parse).
mach12:plan-comment-contract
Apply the canonical contract for a durable implementation-plan comment.
mach12:issue-create
Create a structured GitHub issue from current context or description.