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/feature-autonomous-start)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-autonomous-start"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-autonomous-start/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/feature-autonomous-start"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-autonomous-start.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.00008 | $0.00269 |
| Opus 5 | $0.00004 | $0.00134 |
| Sonnet 5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
feature-autonomous-start 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 5d 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
1 near-identical copy found in the catalogue:
- aigon-feature-autonomous-start — 86% identical, 12 lines differ
What it actually says
aigon-feature-autonomous-start
Start a feature in autonomous mode with explicit agent/evaluator choices and stop point control.
aigon feature-autonomous-start {{args}} <agents...> [--eval-agent=<agent>] [--stop-after=implement|eval|close]
Usage
# Solo: auto-close after implementation
aigon feature-autonomous-start {{args}} cc
# Fleet: run through eval then stop for manual winner selection
aigon feature-autonomous-start {{args}} cc ag --eval-agent=ag --stop-after=eval
# Status
aigon feature-autonomous-start status {{args}}
Notes
--stop-afterdefaults toclose.- Fleet
--stop-after=closecurrently falls back toevalwith an explanatory message. - The command starts a dedicated AutoConductor tmux session (
{repo}-f{id}-auto(-desc)) and exits immediately. - AutoConductor failure is non-destructive; implementation/eval sessions continue and can be finished manually.
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.
- 5d ago First seen · 32 lines · 8 tokens per session scan A 07d2afa702d4
feature-autonomous-start is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 8d ago), licensed Apache-2.0. It adds 8 tokens to every session and 269 once invoked, about $0.0000 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
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
archive-tasks.en
Archive completed tasks into a date-organized workspace directory.
check-task.en
Check a task's current status and progress.
init-milestones.en
Initialize the repository's standard milestones taxonomy.
create-task.en
Create a task from a natural-language description.
import-issue.en
Import an Issue and create a task.