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-set-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-set-prioritise)<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-set-prioritise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-set-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-set-prioritise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-set-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.00023 | $0.00292 |
| Opus 5 | $0.00012 | $0.00146 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
aigon-set-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-set-prioritise
CRITICAL: Use the CLI below. Do not manually rename inbox specs or assign IDs — the command runs feature-prioritise per member in topological order so depends_on stays valid.
When to use
- Several specs share the same
set: <slug>and live in01-inbox/(no numeric id yet). - Inbox specs reference each other with
depends_onusing slugs (or numeric ids for already-backlog features).
Step 1: Run the CLI
aigon set-prioritise $ARGUMENTS
Alias: aigon asp <slug>.
This assigns sequential feature ids and prioritises each member to backlog in an order consistent with intra-set dependencies.
Step 2: Next steps
After prioritisation, start work on the first backlog member (or the whole set in Pro):
aigon-feature-start <ID> <agent>
For set-level autonomous execution (Pro):
aigon-set-autonomous-start <slug> <agents...>
Prompt Suggestion
End with the suggested next command, using a real id from the CLI output:
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 · 44 lines · 23 tokens per session scan A fce144cdf118
aigon-set-prioritise is a skill published in the GitHub repository jayvee/aigon (25 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 292 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
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
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-goal-gate
Ground a keep-working goal in evidence the worker did not author by wiring dos hook stop to refuse false done claims. Use for one self-stopping agent or loop worker; use dos-witness-claim for fold barriers.
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-supervise-loop
Keep a target count of dispatch loops alive across the workspace lane roster: spawn missing loops, scavenge stalled leases, and surface spinning workers. Use when supervising a DOS dispatch-loop fleet.
dos-witness-claim
Route subagent claims through independent read-back before another agent relies on them. Use at parallel, pipeline, or synthesis barriers where shipped phases, files, rows, messages, or other effects must be witnessed.