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 skills add jayvee/aigon --skill aigon-feature-prioritisegit 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-prioritise)<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-feature-prioritise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-feature-prioritise/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/skills/jayvee/aigon/aigon-feature-prioritise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-feature-prioritise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00379 |
| Opus 5 | $0.00011 | $0.00189 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
aigon-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 9d 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-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 $ARGUMENTS
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.
- 9d ago First seen · 52 lines · 22 tokens per session scan A 771eb04619e2
aigon-feature-prioritise is a skill published in the GitHub repository jayvee/aigon (25 stars, last pushed 8d ago), licensed Apache-2.0. It adds 22 tokens to every session and 379 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
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-replan
Refresh a plan portfolio from evidence: close shipped queue items, update cooldown state, and surface the few decisions an operator must make. Use after dispatch bursts, drained backlogs, or recurring findings.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.