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-feature-cleanupnpx skills add jayvee/aigon --skill aigon-feature-cleanupgit 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/skills/jayvee/aigon/aigon-feature-cleanup)<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-feature-cleanup"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-feature-cleanup.svg" alt="Measured on agentmods" 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.00022 | $0.00488 |
| Opus 5 | $0.00011 | $0.00244 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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 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.
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 $1
# Push branches to origin before deleting
aigon feature-cleanup $1 --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.
- 6d ago First seen · 76 lines · 22 tokens per session scan A f8525ff8be5f
aigon-feature-cleanup is a skill published in the GitHub repository jayvee/aigon (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 488 once invoked, about $0.0001 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.