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-now)<a href="https://agentmods.dev/commands/jayvee/aigon/aigon-feature-now"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/aigon-feature-now.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.00000 | $0.01225 |
| Opus 5 | $0.00000 | $0.00613 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
aigon-feature-now 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 3d 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
100% identical to afn — 6 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-now
Fast-track a feature from idea to implementation in one step. Works in two modes:
- Existing feature: If the name matches a feature in the inbox (
01-inbox/), runs prioritise → setup (Drive) → implement - New feature: If no inbox match, creates the spec from scratch, sets up a Drive branch, and starts implementation
Argument Resolution
If no feature name is provided:
- Ask the user what feature they want to create
- Use a slug-friendly name (lowercase, hyphens, no spaces)
Step 1: Check the inbox for an existing feature
List all files in ./docs/specs/features/01-inbox/ matching feature-*.md.
Compare the provided name/slug against the inbox filenames (partial match is fine — e.g. "ralph" matches feature-ralph-wiggum.md).
- If a match is found → go to Path A: Fast-track existing feature
- If no match → go to Path B: Create new feature
If multiple inbox features match, present the matches and ask the user to pick one.
Path A: Fast-track existing feature
The feature already has a spec in the inbox. Prioritise it, set up Drive mode, and implement.
A1: Explore the codebase
Before starting, explore the codebase to understand the existing architecture, patterns, and code relevant to this feature. Read the existing spec to understand what's planned.
A2: Prioritise
aigon feature-prioritise <inbox-name>
This assigns an ID and prioritises the feature to backlog. Note the assigned ID from the output.
A3: Setup (Drive mode)
aigon feature-start <ID>
This records the in-progress lifecycle state, refreshes the generated view, creates the branch, and creates the implementation log.
A4: Implement
Continue from Step 4: Implement below, using the assigned ID.
Path B: Create new feature
No inbox match — create from scratch using the CLI.
B1: Explore the codebase
Before running the command, explore the codebase to understand the existing architecture, patterns, and code relevant to this feature. Consider:
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.
- 3d ago First seen · 145 lines · 0 tokens per session scan A 2443f082c643
aigon-feature-now is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,225 tokens. A static security scan graded it A with 0 findings. It is 100% identical to afn, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
refine-title.en
Rewrite an Issue or PR title in Conventional Commits format.
commit.en
Commit the current changes to Git.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.