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 26BB/agentic-awesome-skills-mcp --skill antigravity-maintainer-batch-releasegit clone --depth 1 https://github.com/26BB/agentic-awesome-skills-mcpWrote 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/26bb/agentic-awesome-skills-mcp/antigravity-maintainer-batch-release)<a href="https://agentmods.dev/skills/26bb/agentic-awesome-skills-mcp/antigravity-maintainer-batch-release"><img src="https://agentmods.dev/badge/skills/26bb/agentic-awesome-skills-mcp/antigravity-maintainer-batch-release/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/26bb/agentic-awesome-skills-mcp/antigravity-maintainer-batch-release"><img src="https://agentmods.dev/badge/skills/26bb/agentic-awesome-skills-mcp/antigravity-maintainer-batch-release.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.03940 |
| Opus 5 | $0.00028 | $0.01970 |
| Sonnet 5 | $0.00011 | $0.00788 |
| Haiku 4.5 | $0.00006 | $0.00394 |
Grade A, and why
antigravity-maintainer-batch-release 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 7d 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
89% identical to antigravity-maintainer-batch-release — 42 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity Maintainer Batch Release
When to Use
Use this skill for repository-wide AAS maintenance, maintainer-side PR repair or merge batches, canonical synchronization, AAS Core or Workbench changes, protected releases, and hosted catalog or legacy redirect infrastructure. Do not use it for ordinary contribution work that does not require maintainer privileges or canonical convergence.
Protected-Main Contract
Treat the repository root containing this skill as pull-request-only:
- Read
AGENTS.md,.github/MAINTENANCE.md, and current maintainer docs before mutation. - Never commit or push directly to
main, even when the user says “push to main.” That phrase names the final target state. - Preserve unrelated dirty work. Use a clean temporary clone or a topic branch for maintainer changes.
- Use
npm run merge:batchfor accepted source PRs. Do not substitute a raw merge API, generic GitHub skill, or generic push helper. - Let
automation/canonical-repo-stateown generated artifacts and contributor-credit convergence after the source batch. - Use
release:prepareandrelease:publishfor releases. They never authorize a directmainpush.
Source Checks
Before changing anything:
- Fetch
origin/main; prove the clean maintainer checkout is onmainand equalsorigin/main. - Inspect live PRs, issues, discussions in scope, Actions failures, Dependabot, CodeQL, secret scanning, and
npm auditwhere relevant. - Confirm current scripts from
package.json; do not rely on remembered release behavior. - Capture user worktree status separately and keep those files out of maintainer commits.
Maintainer Sweep
- Triage every open PR before editing.
- Separate valid source changes, repairable PRs, conflicts, generated-only noise, promotional links, and unsupported ownership/license changes.
- Review semantics, safety, provenance, risk labels, limitations, source credits, and changed-skill evidence.
- Prefer narrow maintainer repairs on the contributor branch when maintainer edits are enabled.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 173 lines · 57 tokens per session scan A 9fc5b3901182
antigravity-maintainer-batch-release is a skill published in the GitHub repository 26BB/agentic-awesome-skills-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 3,940 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to antigravity-maintainer-batch-release, differing in 42 lines, and is treated as a copy.
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.