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-prioritise)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-prioritise"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-prioritise.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.00014 | $0.00387 |
| Opus 5 | $0.00007 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
feature-prioritise 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
89% identical to afp — 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.
What it actually says
aigon-feature-prioritise
CRITICAL: You MUST use the CLI command below to prioritise. Do NOT manually rename or move spec files or lifecycle-view links — the CLI handles ID assignment, workflow state, and view refresh.
Argument Resolution
If no name is provided, or the name doesn't match an existing feature in the inbox:
- List all files in
./docs/specs/features/01-inbox/matchingfeature-*.md - If a partial name was given, filter to files containing that text
- Present the matching features and ask the user to choose one
Step 1: Run the CLI command
aigon feature-prioritise {{args}}
This assigns or confirms the feature ID, records backlog lifecycle state, and refreshes the generated view.
Step 2: Next steps
Choose your mode:
Drive (branch) — work in the current repo:
/aigon:feature-start <ID>
Drive (worktree) — isolated worktree for parallel development:
/aigon:feature-start <ID> <agent>
Fleet — multiple agents compete on the same feature:
/aigon:feature-start <ID> <agent1> <agent2> [agent3...]
Example Drive worktree: /aigon:feature-start 55 cc
Example Fleet: /aigon:feature-start 55 cc ag cx cu
Prompt Suggestion
End your response with the suggested next command on its own line. This helps agent UIs surface the next suggested Aigon command. Use the actual ID assigned by the CLI:
/aigon:feature-start <ID>
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 · 51 lines · 14 tokens per session scan A b3b4e8f5cb8b
feature-prioritise is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 14 tokens to every session and 387 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to afp, 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.