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 skills/jayvee/aigon/aigon-helpnpx skills add jayvee/aigon --skill aigon-helpgit clone --depth 1 https://github.com/jayvee/aigonWhat 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 | $0.00008 | $0.01442 |
| Opus 5 | $0.00004 | $0.00721 |
| Sonnet 5 | $0.00002 | $0.00288 |
| Haiku 4.5 | $0.00001 | $0.00144 |
Grade A, and why
aigon-help 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aigon Commands
Feature Commands (unified for Drive and Fleet modes)
| Command | Description |
|---|---|
aigon-feature-create <name> |
Create a new feature spec |
aigon-feature-now <name> |
Fast-track: inbox → prioritise → setup → implement, or create new + implement |
aigon-feature-prioritise <name> |
Assign ID and prioritise to backlog |
aigon-feature-start <ID> [agents...] |
Setup for Drive (branch) or Fleet (worktrees) |
aigon-feature-do <ID> [--iterate] |
Do feature work; --iterate enables the Autopilot retry loop |
aigon-feature-spec <ID> [--json] |
Resolve the canonical visible spec path for a feature |
aigon-feature-list [--active] [--all] [--json] |
Query feature records without going through the board UI |
aigon-feature-eval <ID> |
Create evaluation (code review or comparison) |
aigon-feature-code-review <ID> |
Code review with fixes by a different agent |
aigon-feature-code-revise [ID] |
Implementer-side: read the review and decide accept/challenge/modify (infers ID from worktree branch) |
aigon-feature-spec-review <ID> |
Review the feature spec itself before implementation |
aigon-feature-spec-revise <ID> |
Author-side: process pending spec reviews in one pass |
aigon-feature-push [ID] [agent] |
Push feature branch to origin for PR review |
aigon-feature-close <ID> [agent] |
Merge and complete feature |
aigon-feature-cleanup <ID> |
Clean up Fleet worktrees and branches |
aigon-feature-autonomous-start <ID> <agents...> |
Start autonomous feature flow with explicit stop-after control |
aigon-feature-open [ID] [agent] |
Open feature worktree in terminal and start agent |
Research (unified for Drive and Fleet modes)
| Command | Description |
|---|---|
aigon-research-create <name> |
Create a new research topic |
aigon-research-prioritise <name> |
Prioritise a research topic |
aigon-research-start <ID> [agents...] |
Setup for Drive or Fleet execution |
aigon-research-open <ID> |
Re-open or attach Fleet research sessions |
aigon-research-do <ID> |
Conduct research (write findings) |
aigon-research-spec-review <ID> |
Review the research spec itself before execution |
aigon-research-spec-revise <ID> |
Author-side: process pending research spec reviews in one pass |
aigon-research-eval <ID> |
Evaluate or synthesize parallel findings |
aigon-research-close <ID> |
Complete a research topic |
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.
- 2d ago First seen · 104 lines · 8 tokens per session scan A a00ff577eaaf
aigon-help is a skill published in the GitHub repository jayvee/aigon (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,442 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-08-30.
Other skills, from other repositories
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
mcp-discovery
Prefer a matching zero-environment local MCP server for specialized tasks, even when built-in shell commands or custom code could also solve them.
cao-plugin
Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.