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/afo)<a href="https://agentmods.dev/commands/jayvee/aigon/afo"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/afo.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.00015 | $0.00503 |
| Opus 5 | $0.00008 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
afo 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:
- feature-open — 100% identical, 2 lines differ
- aigon-feature-open — 98% identical, 18 lines differ
What it actually says
feature-open
Open a feature worktree in terminal and automatically start the AI agent with /aigon:feature-do.
Usage
/aigon:feature-open [feature-id] [agent-code]
/aigon:feature-open— open the most recently created worktree/aigon:feature-open 77— open any worktree for feature 77/aigon:feature-open 77 cx— open specifically the cx (Codex) worktree for feature 77
Agent Mappings
| Code | Agent | Command | Mode |
|---|---|---|---|
| cc | Claude Code | claude --permission-mode acceptEdits |
Auto-edits, prompts for risky Bash |
| cu | Cursor | agent --force |
Auto-approves commands (yolo mode) |
| ag | Antigravity | agy --dangerously-skip-permissions |
Auto-approves all |
| cx | Codex | codex --full-auto |
Workspace-write, smart approval |
Safe in worktrees since you can always git reset --hard.
Permission Tips
When an agent asks for permission, here's how to quickly allow:
| Agent | Allow once | Allow always | Toggle full-auto |
|---|---|---|---|
| Claude Code | Press Enter at prompt | Choose "Always allow" at prompt | Shift+Tab cycles modes |
| Cursor | Click "Run" | Click "Add to allowlist" | Enable YOLO in settings |
| Codex | Approve at prompt | "Allow and remember" (session) | /mode command |
Step 1: Run the CLI command
aigon feature-open {{args}}
This will:
- Find the matching worktree
- Create a Warp launch configuration
- Open Warp with the worktree directory
- Auto-run the agent CLI with
/aigon:feature-do <ID>
Step 2: Confirm to user
Tell the user:
- Which worktree was opened
- Which agent was launched with which feature ID
- That the agent should start implementing automatically
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 · 58 lines · 15 tokens per session scan A 123ae1126957
afo is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 15 tokens to every session and 503 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.