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.
npx agentmods add commands/jayvee/aigon/aigon-feature-dogit 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-feature-do)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-feature-do"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-do.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.00000 | $0.01607 |
| Opus 5 | $0.00000 | $0.00804 |
| Sonnet 5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
aigon-feature-do 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.
This is a copy
98% identical to afd — 12 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-do
RUN THIS FIRST — no preamble, no --help, no file searches:
aigon feature-do <name>This prints the feature spec inline. Read the output, then follow the steps below. Do NOT search for spec files, do NOT run
aigon --help, do NOT hunt for theaigonsource. Just run the command above.
Implement a feature. Works in Drive mode (branch), Drive worktree, and Fleet mode (competition).
Worktree invariant: you are already inside the correct repo. If
aigonfails, read the error — do NOT try to introspect the tool's internals.
Argument Resolution
If no ID is provided or it doesn't match an active feature, run aigon feature-list --active, filter to matches, and ask the user which one.
Step 1: Attach to the workspace
aigon feature-do <name>
Only run /aigon-feature-start <name> if the feature branch/worktree does not exist yet.
To run in Autopilot mode — iterate loop where a fresh agent session is spawned each iteration until validation passes:
aigon feature-do {{ARG1_SYNTAX}} --iterate
Optional flags: --max-iterations=N (default 5) · --agent=<id> · --dry-run
What is iterate mode? The iterate technique runs an agent in a loop: implement → validate → if fail, repeat with fresh context until success or max iterations. Add a
## Validationsection to your feature spec to define feature-specific checks alongside project-level validation.
If the CLI fails with "Could not find feature in in-progress" and you're in a worktree: the spec move was likely not committed before the worktree was created. Fix by running these commands from the worktree:
SPEC_PATH=$(aigon feature-spec {{ARG1_SYNTAX}})
git checkout main -- "$SPEC_PATH"
git commit -m "chore: sync spec to worktree branch"
Step 2: Read the spec (already inlined)
The spec body was printed inline by feature-do above. Use that copy. Do not re-read from disk and do not re-run aigon feature-spec — the inline copy is authoritative.
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 · 121 lines · 0 tokens per session scan A 47348d483132
aigon-feature-do is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,607 tokens. A static security scan graded it A with 0 findings. It is 98% identical to afd, differing in 12 lines, and is treated as a copy.
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.
mach12:plan-comment-contract
Apply the canonical contract for a durable implementation-plan comment.
update-config
Update Dark Flow project settings: language and/or main branch.
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.