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/ab)<a href="https://agentmods.dev/commands/jayvee/aigon/ab"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/ab/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/ab"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/ab.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.00012 | $0.01160 |
| Opus 5.5 | $0.00005 | $0.00464 |
| Sonnet 5.5 | $0.00002 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
ab 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
2 near-identical copies found in the catalogue:
- board — 95% identical, 2 lines differ
- aigon-board — 95% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-board
Visualize features and research topics in Kanban board or detailed list view.
IMPORTANT:
- After running the command, display the board output directly in your response text (not just as a tool result) so the user can see it without expanding collapsed output. Copy the full output verbatim into a code block in your response.
- The board output includes
→ /commandaction hints — make sure these are visible in your response, as they are the primary value of the board. - When suggesting what to work on next, reference items by their letter labels (e.g., "You could prioritize item c) create-plugin") and use the agent's native Aigon command format for suggestions (e.g.,
/aigon:feature-prioritise c) rather than rawaigon ...CLI syntax.
aigon board {{args}}
Views
Default (Kanban): Visual board showing items across workflow stages
aigon board
List view: Detailed list with work mode indicators
aigon board --list
Filters
- No filters: Shows both features and research (excludes done by default)
--features: Show only features--research: Show only research topics--active: Only in-progress items--all: Include completed items--inbox: Only inbox (unprioritized)--backlog: Only backlog (prioritized, waiting)--done: Only completed items--no-actions: Suppress→ /commandaction hints (clean view for scripting)
Indicators (Kanban View)
*= current active branch[F]= Fleet mode[AP]= Autopilot modea), b), c)...= letter shortcuts for quick prioritization
Quick Prioritize
Unprioritized inbox items show letter labels. Use them for quick prioritization:
# After running 'aigon board' and seeing:
# a) base-port-config
# b) create-plugin
aigon feature-prioritise b # Quickly prioritizes "create-plugin"
aigon research-prioritise i # Works for research too
Letters are saved in .aigon/.board-map.json (expires after 24 hours).
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 · 133 lines · 12 tokens per session scan A 934920de4ca3
ab is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 17d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,160 once invoked, about $0.0000 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-08-30.
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.