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/aigon-research-open)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-research-open"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-research-open.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.00000 | $0.00551 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
aigon-research-open 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.
This is a copy
94% identical to research-open — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-research-open
Open all Fleet research agents side-by-side in Warp terminal, each pre-loaded with the research-do command.
Usage
/aigon-research-open <research-id>
/aigon-research-open 05— opens all Fleet agents side-by-side for research 05
When to Use
This command is for Fleet mode research only. It opens multiple terminal panes (one per agent) so you can run parallel research.
Prerequisites:
- Research must be set up in Fleet mode:
aigon research-start <ID> cc ag cx - Findings files must exist in
docs/specs/research-topics/logs/
What It Does
- Detects which agents are set up by scanning findings files
- Opens Warp terminal with horizontal split panes (one per agent)
- Each pane is pre-loaded with the agent CLI and
/aigon-research-do <ID>command - All panes use the main repository directory (not separate worktrees)
Example
After running:
aigon research-start 05 cc ag cx
You can open all agents side-by-side:
aigon research-open 05
This opens Warp with 3 panes:
- Pane 1 (cc):
claude --permission-mode acceptEdits "/aigon:research-do 05" - Pane 2 (ag):
agy --dangerously-skip-permissions(aigon inlines theresearch-doprompt body at launch) - Pane 3 (cx):
codex --full-auto(aigon inlines theresearch-doprompt body at launch;$aigon-research-dois also available as a Skill mention inside Codex)
Error Cases
- Not in Fleet mode: Shows error with instructions to run
research-startwith agents - Research not found: Shows error if research ID doesn't exist or isn't in progress
- Agent not configured: Lists which agents need to be installed
Step 1: Run the CLI command
Always run this command — do NOT skip it or try to detect the terminal yourself. The CLI reads the user's terminal preference from ~/.aigon/config.json and handles everything:
aigon research-open <args>
Step 2: Confirm to user
Tell the user:
- Which agents are being opened
- That each pane will have the research-do command pre-loaded
- That they should run the command in each pane to start research
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 · 67 lines · 0 tokens per session scan A a78154fe5259
aigon-research-open is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 551 tokens. A static security scan graded it A with 0 findings. It is 94% identical to research-open, differing in 13 lines, and is treated as a copy.
Other commands, from other repositories
pick-agent
A command that helps users choose and import only the agent role they need, such as a frontend developer, researcher, or editor.
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.