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 skills add jayvee/aigon --skill aigon-research-spec-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-research-spec-revise)<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-research-spec-revise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-research-spec-revise/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jayvee/aigon/aigon-research-spec-revise"><img src="https://agentmods.dev/badge/skills/jayvee/aigon/aigon-research-spec-revise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00487 |
| Opus 5 | $0.00012 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
aigon-research-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 10d 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.
What it actually says
aigon-research-spec-revise
You are the author-side agent. Review all pending spec-review: commits on the research 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=$(find docs/specs/research-topics -maxdepth 2 \( -name "research-$1-*.md" -o -name "research-$1.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.
Find pending review commits
LAST_ACK=$(git log --follow --format=%H -n 1 --grep='^spec-review-check:' --grep='^spec-revise:' -- "$SPEC_PATH")
echo "last_ack=${LAST_ACK:-none}"
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. Accept, revert, or modify the reviewed changes, then leave the spec in its final state.
Acknowledge with one commit
git add "$SPEC_PATH"
git commit --allow-empty -m "spec-revise: research $1 — <decision summary>" -m "reviewed: <comma-separated reviewer ids>
Decision:
- <accept|revert|modify summary>
Notes:
- <important rationale>"
aigon research-spec-revise-record $1
Report
Tell the user:
- Which pending reviews you processed.
- Whether you accepted, reverted, or modified the reviewed changes.
- Any follow-up edits you made to the spec.
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.
- 10d ago First seen · 66 lines · 23 tokens per session scan A e7fd0647768e
aigon-research-spec-revise is a skill published in the GitHub repository jayvee/aigon (25 stars, last pushed 9d ago), licensed Apache-2.0. It adds 23 tokens to every session and 487 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
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
do
Work an increment task by task through the ledger: task next, claim, implement, commit, task done with evidence. Use when saying "implement", "start working", or "continue increment".
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
conventional-commits
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
commit-analyzer
Analyze git commit frequency, categories, and timing patterns to diagnose autonomous agent activity and operational health.
issue-to-pr
Implement one bounded repository issue with normal host tools, prove the tested change through one scafld finalize wall, and optionally publish the exact pull request through scoped provider authority with readback.