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 agentmods add skills/jayvee/aigon/aigon-feature-code-revisenpx skills add jayvee/aigon --skill aigon-feature-code-revisegit 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-feature-code-revise)<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-feature-code-revise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-feature-code-revise.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 | $0.00024 | $0.01227 |
| Opus 5 | $0.00012 | $0.00613 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
aigon-feature-code-revise 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-code-revise
A reviewing agent has just committed fixes (or notes) on this feature branch. Your job — as the implementing agent — is to read what the reviewer did, then decide how to respond: accept, revert, or modify.
Step 0: Resolve the feature ID
If the user already passed an explicit feature ID as the command argument, use that ID and skip to Step 1.
Otherwise — the primary path — infer the ID from the current branch. You should be running this inside the implementation worktree:
BRANCH=$(git branch --show-current)
echo "Branch: $BRANCH"
Expected branch shape: feature-<slug>-<agent> (e.g. feature-check-review-skill-command-cc).
Parse the <slug> out of the branch name (strip the feature- prefix and the trailing -<agent> suffix where agent is one of cc, cx, cu, op, km, am, ag, cp). Then resolve the slug to a feature ID by matching against aigon feature-list --active:
aigon feature-list --active
Find the row whose name matches the slug and read its ID.
If the branch is main or doesn't match the feature-<slug>-<agent> pattern: STOP. Print this one-liner and do nothing else:
Can't infer feature ID — run this inside the feature worktree, or pass an explicit ID (e.g.
aigon-feature-code-revise 230).
Do not guess. Do not prompt the user to pick from a list — that's noise. Just stop.
Step 1: Signal start of revision
Before reading the review, signal that you are now actively addressing the code review. This makes the dashboard reflect what you're doing in real time, and emits a lifecycle event the AutoConductor uses to detect stalls.
aigon agent-status addressing-code-review
Step 2: Find the review commits
Look at every commit on this branch that came from a reviewer:
git log --oneline --grep='^fix(review)\|^docs(review)' main..HEAD
For broader context (your own implementation commits too), also run:
git log --oneline main..HEAD
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.
- 4d ago First seen · 123 lines · 24 tokens per session scan A 6369b16e1049
aigon-feature-code-revise is a skill published in the GitHub repository jayvee/aigon (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 1,227 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.