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 lingxling/awesome-skills-cn --skill antigravity-maintainer-batch-releasegit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/antigravity-maintainer-batch-release)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/antigravity-maintainer-batch-release"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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/lingxling/awesome-skills-cn/antigravity-maintainer-batch-release"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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.07805 |
| Opus 5.5 | $0.00023 | $0.03122 |
| Sonnet 5.5 | $0.00011 | $0.01561 |
| Haiku 4.5 | $0.00006 | $0.00781 |
Grade B, and why
antigravity-maintainer-batch-release scanned grade B 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
- Prose dominates. Roughly nine in ten findings sit in `SKILL.md`, README, and `references/**` prose. A security reference that documents `Ignore all previous instructions` or `.env` handling is describing an attack, not Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 273 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. That lane runssync:repo-state, which now also recomputes the README## Top Contributorsleaderboards throughsync:top-contributors: never hand-edit those tables, and treat a stale ranking as a generator or exclusion-list defect instead. - 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.jsonand the workflow files listed in Current CI workflow; do not rely on remembered CI or release behavior. - Capture user worktree status separately and keep those files out of maintainer commits.
Current CI workflow
Read .github/workflows/ci.yml, .github/workflows/skill-review.yml, .github/workflows/skillspector-advisory.yml, and their protected-base scripts on the exact task base. Job dependencies define execution order; file order and a green workflow badge do not define merge authority.
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.
- 9d ago First seen · 273 lines · 57 tokens per session scan B 16e11ec14012
antigravity-maintainer-batch-release is a skill published in the GitHub repository lingxling/awesome-skills-cn (310 stars, last pushed 9d ago), licensed MIT. It adds 57 tokens to every session and 7,805 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-07.
Other skills, from other repositories
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…