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/feature-code-review)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-code-review"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-code-review.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.00014 | $0.02363 |
| Opus 5 | $0.00007 | $0.01182 |
| Sonnet 5 | $0.00003 | $0.00473 |
| Haiku 4.5 | $0.00001 | $0.00236 |
Grade A, and why
feature-code-review 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
98% identical to afr — 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-code-review
Perform a code review on another agent's implementation, making targeted fixes where needed. Use a different model than the implementer for best results.
You are doing a write-capable review pass, not a read-only review report. Ignore any default "code review means findings-only" behavior for this task; this command is specifically a review-with-fixes workflow.
Your default action is:
- identify a concrete issue
- patch it in the feature worktree
- commit it with
fix(review): ... - leave only residual issues in notes
Do not stop at describing a fix if you can safely make it yourself. A findings-only review is valid only when:
- the implementation is genuinely clean
- the remaining issue requires a broader architectural or product decision
- the issue is ambiguous and the correct behavior is not clear from the spec
- you are blocked by missing context or infrastructure you cannot safely change
Argument Resolution
If no ID is provided or doesn't match an active feature, run aigon feature-list --active, filter to matches, and ask the user.
Step 1: Gather all context (one tool call)
Run this entire block in a single shell execution — do not split it up. It fetches branch info, the full diff, and the implementation log in one shot so you can review immediately without extra round-trips.
You MUST commit review changes to the FEATURE WORKTREE, never to main.
BRANCH=$(git branch --show-current)
FEATURE_BRANCH=$(git branch --list 'feature-{{args}}-*' | head -1 | tr -d ' *')
WORKTREE=$(git worktree list | grep "feature-{{args}}" | awk '{print $1}')
echo "=== WORKSPACE ==="
echo "Current: $BRANCH Feature: $FEATURE_BRANCH Worktree: $WORKTREE"
echo "=== DIFF ==="
git diff "main...${FEATURE_BRANCH:-HEAD}"
echo "=== IMPLEMENTATION LOG ==="
cat docs/specs/features/logs/feature-{{args}}-*-log.md 2>/dev/null || echo "(no log found)"
aigon agent-status reviewing
The spec body was printed inline by the launching CLI — use that copy for acceptance criteria.
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 · 211 lines · 14 tokens per session scan A 5ef87b48f251
feature-code-review is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,363 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to afr, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
request-review-plan
Request Code Review Phases 1-2: Planning scope and assembling reviewer context.
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.