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-now)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-now"><img src="https://agentmods.dev/badge/commands/jayvee/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.00015 | $0.01259 |
| Opus 5 | $0.00008 | $0.00629 |
| Sonnet 5 | $0.00003 | $0.00252 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
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
98% identical to afn — 2 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 — 149 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 · 149 lines · 15 tokens per session scan A 35c02d418ef5
feature-now is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,259 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to afn, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
archive-tasks.en
Archive completed tasks into a date-organized workspace directory.
block-task.en
Mark a task as blocked and record the reason.
check-task.en
Check a task's current status and progress.
init-milestones.en
Initialize the repository's standard milestones taxonomy.
create-task.en
Create a task from a natural-language description.