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/asp)<a href="https://agentmods.dev/commands/jayvee/aigon/asp"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/asp/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/commands/jayvee/aigon/asp"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/asp.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00308 |
| Opus 5.5 | $0.00010 | $0.00123 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
asp 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 1mo 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
95% identical to set-prioritise — 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-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 {{args}}
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.
- 1mo ago First seen · 44 lines · 24 tokens per session scan A 19d8a72d2b9e
asp is a command published in the GitHub repository jayvee/aigon (26 stars, last pushed 12d ago), licensed Apache-2.0. It adds 24 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to set-prioritise, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
mach12:gh-issue-read
Read a GitHub issue's title, body, and all comments; optionally locate an HTML-marker comment.
mach12:gh-assign
Assign the current user to one or more GitHub issues, handling existing assignees.
mach12:gh-sub-issues
Detect sub-issues of a GitHub issue using the two-strategy approach (API, then body-parse).
mach12:plan-comment-contract
Apply the canonical contract for a durable implementation-plan comment.
mach12:issue-create
Create a structured GitHub issue from current context or description.