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/next)<a href="https://agentmods.dev/commands/jayvee/aigon/next"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/next.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.00011 | $0.01536 |
| Opus 5 | $0.00005 | $0.00768 |
| Sonnet 5 | $0.00002 | $0.00307 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
next 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- an — 97% identical, 2 lines differ
- aigon-next — 95% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-next
Inspect the current git branch, worktree status, and Kanban stage to automatically suggest the most likely next workflow action. Eliminates the need to remember command names for the happy path.
Step 1: Gather context
Run all three commands:
git branch --show-current
git status --short
aigon board --list --active
Step 2: Parse the branch name
Extract context from the branch name using the pattern feature-<ID>-<agent>-<description> or research-<ID>-<agent>-<description>:
- Type:
featureorresearch - ID: numeric ID (e.g.,
25) - Agent: agent code (e.g.,
cc,ag,cx,cu) — if absent, this is a Drive branch - Description: slug description
Drive vs worktree: if the agent segment is one of cc, ag, cx, cu, this is a Fleet worktree branch — feature-do runs automatically on open and must NOT be suggested. If the agent segment is absent (branch is feature-<ID>-<description>), this is a Drive branch — feature-do must be run manually.
If the branch is main (or master), skip to Path D: Main branch.
Step 3: Apply the decision tree
Path A: Feature branch with uncommitted changes
Condition: Branch matches feature-<ID>-* AND git status --short is non-empty
Suggestion:
You have uncommitted changes on feature branch
<branch>.Suggested next step: Commit your changes, update your feature log, then run:
aigon agent-status implementation-completeImplementation is only complete after
aigon agent-status implementation-completesucceeds.
Path B: Feature branch with no uncommitted changes
Condition: Branch matches feature-<ID>-* AND git status --short is empty
Check: Run git log main..HEAD --oneline to count commits on this branch beyond the base. Also check whether this is a Drive branch (no agent code) or a worktree branch (agent code present).
B1: Drive branch, no implementation commits yet (only the spec-move commit or zero commits)
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 · 191 lines · 11 tokens per session scan A 3e09a6933bbc
next is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,536 once invoked, about $0.0001 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
create-issue
Create a GitHub issue with proper template discovery and population.
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
update-config
Update Dark Flow project settings: language and/or main branch.
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.
status
Cross-project status check — pull current state from /CLAUDE.md + vault + git.