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/arsr)<a href="https://agentmods.dev/commands/jayvee/aigon/arsr"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/arsr.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.00020 | $0.01438 |
| Opus 5 | $0.00010 | $0.00719 |
| Sonnet 5 | $0.00004 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
arsr 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
94% identical to research-spec-review — 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-research-spec-review
Review the research topic spec itself, not the findings. Edit the spec in place using the shared rubric below, then commit the reviewed spec with a spec-review: commit.
Your job: WRITE a review of this research spec. That means reading it, making targeted edits in place, and creating one spec-review: commit that records your findings. You are the reviewer. Do not check for or process anyone else's reviews — that is a separate downstream task (research-spec-revise) and is not what you are doing here.
If git log shows no prior spec-review: commits on this spec, that is expected — your review will be the first. Do not exit with "no pending reviews"; that would be the check workflow, not this one.
You are already inside the spec-review task for this research topic.
- Do not run
aigon research-spec-review {{args}}again. - Do not run
aigon research-spec-revise {{args}}— that is a different command for a later stage, run by the research author after reviewers have completed their review. It is not your job here. - Do not ask the shell to start the same command recursively.
- Use the resolved spec path below, edit that spec in place, then make the required
spec-review:commit and runaigon research-spec-review-record {{args}}. - If you cannot complete the commit or record step, stop and report the blocker instead of making a generic commit.
Resolve the spec
SPEC_PATH=$(find docs/specs/research-topics -maxdepth 2 \( -name "research-{{args}}-*.md" -o -name "research-{{args}}.md" \) | head -1)
test -n "$SPEC_PATH" && echo "$SPEC_PATH"
If SPEC_PATH is empty, stop and report that the research spec could not be resolved.
Read the spec:
cat "$SPEC_PATH"
Review rubric
Spec Review Rubric
Review the spec against this checklist. Prefer small, targeted edits over broad rewrites.
Specificity
- Replace vague language with concrete behavior, constraints, and outcomes.
- Name exact commands, files, states, and data shapes where they matter.
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 · 140 lines · 20 tokens per session scan A f6f18130e078
arsr is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,438 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to research-spec-review, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
pick-agent
A command that helps users choose and import only the agent role they need, such as a frontend developer, researcher, or editor.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.