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.
npx agentmods add commands/jayvee/aigon/research-closegit 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/research-close)<a href="https://agentmods.dev/commands/jayvee/aigon/research-close"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/research-close.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 | $0.00009 | $0.00257 |
| Opus 5 | $0.00005 | $0.00129 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
research-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 yesterday.
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
2 near-identical copies found in the catalogue:
- arcl — 94% identical, 2 lines differ
- aigon-research-close — 88% identical, 8 lines differ
What it actually says
aigon-research-close
Run this command followed by the Research ID.
aigon research-close {{args}}
Argument Resolution
If no ID is provided, or the ID doesn't match an existing topic in evaluation or in progress:
- List all files in
./docs/specs/research-topics/04-in-evaluation/and./docs/specs/research-topics/03-in-progress/matchingresearch-*.md - If a partial ID or name was given, filter to matches
- Present the matching topics and ask the user to choose one
This records the research topic as done and refreshes the generated lifecycle view.
Usage
After evaluation: Run after research-eval has completed — the standard parallel-work flow.
Drive mode: Run after research-do is complete and the research pass is ready to finish.
Skipping eval: Closing from in-progress (without running eval) will show a warning but proceed. This is most relevant for single-agent research, just as feature close can skip comparative evaluation when there is nothing to compare.
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.
- yesterday First seen · 31 lines · 9 tokens per session scan A 1db8c916b061
research-close is a command published in the GitHub repository jayvee/aigon (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 257 once invoked, about $0.0000 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-03.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.