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-prioritise)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-research-prioritise"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-research-prioritise/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-prioritise"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-research-prioritise.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.00220 |
| Opus 5.5 | $0.00000 | $0.00088 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
aigon-research-prioritise 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-prioritise — 10 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-prioritise
Run this command followed by the research topic name.
aigon research-prioritise <args>
Argument Resolution
If no name is provided, or the name doesn't match an existing topic in the inbox:
- List all files in
./docs/specs/research-topics/01-inbox/matchingresearch-*.md - If a partial name was given, filter to files containing that text
- Present the matching topics and ask the user to choose one
This assigns or confirms the research ID, records backlog lifecycle state, and refreshes the generated view.
Next step: Run /aigon-research-start <ID> (Drive) or /aigon-research-start <ID> cc ag (Fleet) to begin.
Prompt Suggestion
End your response with the suggested next command on its own line. This helps agent UIs surface the next suggested Aigon command. Use the actual ID assigned by the CLI:
/aigon-research-start <ID>
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 · 25 lines · 0 tokens per session scan A 5bb75a6b7848
aigon-research-prioritise is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 220 tokens. A static security scan graded it A with 0 findings. It is 88% identical to research-prioritise, differing in 10 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.