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 agents/jayvee/aigon/codexgit 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.00000 | $0.01761 |
| Opus 5 | $0.00000 | $0.00881 |
| Sonnet 5 | $0.00000 | $0.00352 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
codex 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 yesterday.
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
95% identical to amp — 100 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Configuration
Agent Identity
- Agent ID:
cx - Worktree Pattern:
../feature-NN-cx-description - Implementation Log: Default-required in all modes — solo Drive branch and worktree need at least a one-line log under
./docs/specs/features/logs/; Fleet needs a short structured log. Opt out only with"logging_level": "never"in.aigon/config.json(see.aigon/docs/development_workflow.md).
Commands
Feature Commands (unified for Drive and Fleet modes)
| Command | Description |
|---|---|
$aigon-feature-create <name> |
Create a new feature spec |
$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] |
Implement feature; --iterate runs Autopilot retry loop |
$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-close <ID> [agent] |
Merge and complete feature |
$aigon-feature-push [ID] [agent] |
Push feature branch to origin for PR review |
$aigon-feature-autonomous-start <ID> <agents...> |
Start autonomous feature flow with explicit stop-after control |
$aigon-feature-cleanup <ID> |
Clean up Fleet worktrees and branches |
Research Commands (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 when needed |
$aigon-research-do <ID> |
Conduct research (write findings) |
$aigon-research-review <ID> |
Review research findings with a different agent |
$aigon-research-eval <ID> |
Synthesize findings before close |
$aigon-research-close <ID> |
Complete 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.
- yesterday First seen · 131 lines · 0 tokens per session scan A e8c00ee1cab2
codex is an agent published in the GitHub repository jayvee/aigon (23 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,761 tokens. A static security scan graded it A with 0 findings. It is 95% identical to amp, differing in 100 lines, and is treated as a copy.
Other agents, from other repositories
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.