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/feedback-triage)<a href="https://agentmods.dev/commands/jayvee/aigon/feedback-triage"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feedback-triage.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.00010 | $0.00415 |
| Opus 5 | $0.00005 | $0.00208 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
feedback-triage 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
91% identical to afbt — 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-feedback-triage
Run a triage loop for one feedback item with explicit human confirmation before writes.
Step 1: Load context
Run:
aigon feedback-triage {{args}}
Then gather broader context:
aigon feedback-list --all
Step 2: Produce triage recommendation
Use the feedback file content plus CLI output to propose:
typeseveritytags- duplicate candidates (based on title + summary similarity)
- next action: keep, mark duplicate, promote to feature, promote to research, wont-fix
When duplicates are plausible, include candidate IDs with rationale.
Step 3: Ask for confirmation (required)
Before writing anything, present the proposed values and ask the user to confirm.
Do not apply triage changes until the user explicitly says yes.
Step 4: Apply only after confirmation
After confirmation, run:
aigon feedback-triage {{args}} --type <type> --severity <severity> --tags <tag1,tag2> --status <status> [--duplicate-of <ID>] --apply --yes
Notes:
- Use
--severity noneto clear severity - Use
--tags noneto clear tags - Use
--duplicate-of noneto clear duplicate linkage - Duplicate status requires
duplicate_of
Step 5: Verify outcome
Confirm the command output shows:
- front matter updates applied
- file moved to the correct feedback lifecycle folder for the new status
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 · 60 lines · 10 tokens per session scan A f0e4b5d00557
feedback-triage is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 10 tokens to every session and 415 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to afbt, 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.
check-task.en
Check a task's current status and progress.
create-task.en
Create a task from a natural-language description.
import-issue.en
Import an Issue and create a task.
init-milestones.en
Initialize the repository's standard milestones taxonomy.