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-spec-revise)<a href="https://agentmods.dev/commands/jayvee/aigon/feature-spec-revise"><img src="https://agentmods.dev/badge/commands/jayvee/aigon/feature-spec-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.1 | $0.00015 | $0.00619 |
| Opus 5 | $0.00008 | $0.00309 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
feature-spec-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 5d 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
97% identical to afsrv — 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aigon-feature-spec-revise
You are the author-side agent. Review all pending spec-review: commits on the feature spec, decide what to keep, and land one acknowledgement commit.
The continuity strategy is selected by Aigon before launch. Do not choose a provider or resume strategy yourself. When resumed, reconcile remembered paths against the current checkout and emit the requested continuation ready/fallback checkpoint before editing.
Resolve the spec
SPEC_PATH=$(aigon feature-spec {{args}} 2>/dev/null || true)
if [ -z "$SPEC_PATH" ]; then
SPEC_PATH=$(find docs/specs/features -maxdepth 2 \( -name "feature-{{args}}-*.md" -o -name "feature-{{args}}.md" \) | head -1)
fi
test -n "$SPEC_PATH" && echo "$SPEC_PATH"
If SPEC_PATH is empty, stop and report that the feature spec could not be resolved.
Find pending review commits
Find the latest acknowledgement, if any:
LAST_ACK=$(git log --follow --format=%H -n 1 --grep='^spec-review-check:' --grep='^spec-revise:' -- "$SPEC_PATH")
echo "last_ack=${LAST_ACK:-none}"
Then inspect pending reviews newer than that acknowledgement:
git log --follow --format='%H %s' -- "$SPEC_PATH"
Pending reviews are commits whose subject starts with spec-review: and are newer than LAST_ACK if LAST_ACK exists.
For every pending review commit:
git show <sha> -- "$SPEC_PATH"
git show -s --format=%B <sha>
Decide in one pass
Process all pending reviewers together. Your options are:
- Accept: keep the reviewed spec as-is.
- Revert: revert one or more review commits.
- Modify: keep the reviewer intent but make follow-up edits before acknowledging.
If you need changes, make them before the acknowledgement commit.
Acknowledge with one commit
After the spec is in its final state, commit exactly once with:
git add "$SPEC_PATH"
git commit --allow-empty -m "spec-revise: feature {{args}} — <decision summary>" -m "reviewed: <comma-separated reviewer ids>
Decision:
- <accept|revert|modify summary>
Notes:
- <important rationale>"
aigon feature-spec-revise-record {{args}}
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.
- 5d ago First seen · 85 lines · 15 tokens per session scan A b590a4215517
feature-spec-revise is a command published in the GitHub repository jayvee/aigon (25 stars, last pushed 7d ago), licensed Apache-2.0. It adds 15 tokens to every session and 619 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to afsrv, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
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.
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.
commit.en
Commit the current changes to Git.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.
refine-title.en
Rewrite an Issue or PR title in Conventional Commits format.