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-cleanup)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-feature-cleanup"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-cleanup/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-cleanup"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-cleanup.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.00460 |
| Opus 5.5 | $0.00000 | $0.00184 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
aigon-feature-cleanup 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 1mo 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
95% identical to feature-cleanup — 9 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.
What it actually says
aigon-feature-cleanup
Remove all worktrees and branches for a feature. Useful after completing a Fleet run or when canceling a feature.
Usage
# Delete worktrees and local branches
aigon feature-cleanup <name>
# Push branches to origin before deleting
aigon feature-cleanup <name> --push
Argument Resolution
If no ID is provided, or the ID doesn't match an existing feature:
- Run
aigon feature-list --active - If a partial ID or name was given, filter to matches
- Present the matching features and ask the user to choose one
What Gets Cleaned Up
This command removes:
- All worktrees for the feature (e.g.,
../feature-55-cc-desc,../feature-55-ag-desc) - All local branches for the feature
- Worktree permissions from Claude settings
Options
--push Flag
Use --push to preserve branches on the remote before deleting locally:
aigon feature-cleanup 55 --push
This will:
- Push each branch to
origin - Delete local branches
- Remove worktrees
Without --push, branches are only deleted locally.
When to Use
After Fleet Completion
After running aigon feature-close 55 <agent> to merge the winning implementation, clean up the losing implementations:
aigon feature-cleanup 55
Canceling a Feature
If you want to abandon a feature that was set up in Fleet mode:
aigon feature-cleanup 55 --push # Preserve work on remote
# or
aigon feature-cleanup 55 # Delete everything
Important Notes
- This command is destructive - deleted worktrees and branches cannot be easily recovered
- Use
--pushif you want to preserve the work on the remote repository - The command will remove ALL branches matching
feature-<ID>-* - For Drive mode features, this will delete the feature branch (use with caution)
- Logs and specs in
docs/specs/features/are NOT deleted
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.
- 1mo ago First seen · 71 lines · 0 tokens per session scan A 883e1665fb5d
aigon-feature-cleanup is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 460 tokens. A static security scan graded it A with 0 findings. It is 95% identical to feature-cleanup, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
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.
mach12:issue-create
Create a structured GitHub issue from current context or description.
mach12:pr-pre-merge
Run the pre-merge checklist - branch freshness, docs, version, CHANGELOG, tests, CI.
mach12:pr-review
Run a comprehensive PR review with independent reviewers and post the results as a structured comment.
mach12:pr-merge
Merge a PR, delete the feature branch, and optionally create a release.