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-close)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-research-close"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-research-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/aigon-research-close"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-research-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.00000 | $0.00236 |
| Opus 5.5 | $0.00000 | $0.00094 |
| Sonnet 5.5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
aigon-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 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.
This is a copy
88% identical to research-close — 8 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.
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:
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 · 27 lines · 0 tokens per session scan A a342e1090765
aigon-research-close is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 17d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 236 tokens. A static security scan graded it A with 0 findings. It is 88% identical to research-close, differing in 8 lines, and is treated as a copy.
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.