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/feature-reset)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-reset"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-reset/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/feature-reset"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-reset.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.00019 | $0.00309 |
| Opus 5.5 | $0.00008 | $0.00124 |
| Sonnet 5.5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
feature-reset 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aigon-feature-reset — 91% identical, 7 lines differ
What it actually says
aigon-feature-reset
Fully reset a feature back to backlog state. Removes all worktrees, branches, manifest state files, and refreshes the lifecycle view.
Usage
aigon feature-reset {{args}}
Argument Resolution
If no ID is provided, or the ID doesn't match an existing feature:
- Run
aigon feature-list --all - If a partial ID or name was given, filter to matches
- Present the matching features and ask the user to choose one
What Gets Reset
This command removes:
- All worktrees for the feature
- All local branches for the feature
- Manifest state files (
.aigon/state/feature-<ID>*.json) - Worktree permissions from Claude settings
- Lifecycle view — refreshed so the feature appears in backlog
When to Use
- Starting over on a feature after a failed attempt
- Resetting a demo/seed project back to clean state
- Canceling an in-progress feature and returning it to backlog
Important Notes
- This command is destructive — all worktree work is lost
- The spec file is preserved (moved to backlog), not deleted
- Remote branches are NOT deleted — only local state is cleaned
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 · 43 lines · 19 tokens per session scan A 17e7ac0acc25
feature-reset is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It adds 19 tokens to every session and 309 once invoked, about $0.0001 per session on Opus 5.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-09-03.
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.