Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AndreVianna/aid-methodologynpx agentmods add skills/andrevianna/aid-methodology/release-aidWrote 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/andrevianna/aid-methodology/release-aid)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/release-aid"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/release-aid/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/andrevianna/aid-methodology/release-aid"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/release-aid.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.00123 | $0.04129 |
| Opus 5 | $0.00062 | $0.02065 |
| Sonnet 5 | $0.00025 | $0.00826 |
| Haiku 4.5 | $0.00012 | $0.00413 |
Grade A, and why
release-aid scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **PyPI:** `curl -s https://pypi.org/simple/aid-installer/ | grep <target-normalized>` — use How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release AID
Maintainer-only skill — outside
canonical/. Likegenerate-profile, this lives only at.claude/skills/release-aid/— it is NOT incanonical/skills/, is NOT rendered toprofiles/, and is NEVER shipped to adopters. It operates on the AID repo itself. Edit it directly. It is a runnable procedure, not a spec — for the format/architecture of a release see.aid/knowledge/infrastructure.md; for the deep runbook (recovery,release.shflags) seedocs/release.md. This skill EXECUTES the process and closes the gap those two leave open: it always updates the release notes as part of the release.
Cuts one release of the AID repo — beta or stable — from the command to artifacts published in the right places with every check green. Runs the whole sequence autonomously, pausing only at the irreversible human-gated points: the PR merge, the tag push, and confirming the publish.
Argument — REQUIRED
/release-aid <level> where <level> is exactly one of major | minor | patch | beta.
The argument is required. If it is missing or not one of the four values, STOP and ask (one clear question) which level to release — do NOT default, guess, or proceed. Only continue once a valid level is chosen.
Step 0 — Resolve the target version
Read the current version: cat VERSION (source of truth; format M.m.p optionally -beta.N).
Never trust a version hard-coded in prose. Compute the target by the level, bumping that level
and zeroing every level below it:
| level | current is stable M.m.p |
current is beta M.m.p-beta.N |
|---|---|---|
major |
(M+1).0.0 (stable) |
(M+1).0.0 (stable) |
minor |
M.(m+1).0 (stable) |
M.(m+1).0 (stable) |
patch |
M.m.(p+1) (stable) |
M.m.p (stable — PROMOTE: drop the -beta.N, do not bump) |
beta |
M.m.(p+1)-beta.1 (start the next patch's beta line) |
M.m.p-beta.(N+1) (next beta of the same target) |
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.
- 9d ago First seen · 292 lines · 123 tokens per session scan A 32bcafcd19e9
release-aid is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 123 tokens to every session and 4,129 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.