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/aigon-feature-transfer)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-feature-transfer"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-transfer/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/aigon-feature-transfer"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-transfer.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.00000 | $0.00733 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
aigon-feature-transfer 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 6d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-transfer
Hand a stuck or paywalled in-progress feature from its current agent to a different agent, without losing commits or in-flight work. Intended for:
- An agent hitting a usage/token limit mid-implementation (Codex paywall, Claude 5h limit).
- An agent stalling on a prompt, auth flow, or tool confusion that won't resolve itself.
- A human deciding that a different agent (e.g. Claude Code) should take over from here.
The worktree, commits, branch, and workflow history are all preserved. Only the active agent changes.
Usage
aigon feature-transfer <name> --to=<agent> [--reason="..."] [--no-launch]
Flags:
--to=<agent>(required) — target agent id (e.g.cc,cx,ag,cu).--reason="..."— free-text reason recorded in the transfer briefing.--no-launch— do the transfer but don't auto-spawn the new agent; handy for scripted orchestration.
What it does (in order)
- Captures the last ~3000 lines from every live tmux pane for the feature.
- Writes a briefing to
docs/specs/features/logs/feature-<ID>-transfer-<timestamp>.md— last commits, uncommitted diff, pane tails, and next-steps for the new agent. - Commits any uncommitted work in the worktree as
wip(transfer): save <old> state before handoff to <new>so nothing is lost by the directory move. - Kills the old agent's tmux sessions and removes its heartbeat file.
- Moves the worktree with
git worktree move— directory renames fromfeature-<ID>-<old>-<desc>/tofeature-<ID>-<new>-<desc>/. The branch name is preserved (it encodes who originally started the work — not a problem, it's cosmetic after merge). - Re-seeds the workflow engine by emitting a fresh
feature.startedevent so the dashboard and snapshot reflect the new agent. Prior events stay in history. - Launches the new agent with
aigon feature-do <ID> --agent=<new>unless--no-launchwas passed.
The new agent's first task is to read the briefing and the wip(transfer) commit before doing anything else — the briefing lays out exactly where the previous agent stopped and why.
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.
- 6d ago First seen · 49 lines · 0 tokens per session scan A d92ffd3d3780
aigon-feature-transfer is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 733 tokens. 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.
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.