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 gabrielmoreira/agent-skills-mirror --skill releasegit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/release)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/release"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/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/gabrielmoreira/agent-skills-mirror/release"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/release.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.00049 | $0.00705 |
| Opus 5 | $0.00024 | $0.00352 |
| Sonnet 5 | $0.00010 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NGINX UI Release
Use this workflow for NGINX UI releases from the repository root.
Preconditions
- Work from the
devbranch. - Inspect
git status --short --branchbefore changing files. - If the user asks to commit existing workspace changes first, inspect recent commit style and commit that work separately before release prep.
- Keep staging explicit. Do not include unrelated local changes.
- Treat
release-notes-vX.Y.Z.mdas a temporary local release artifact, not a committed file.
Version Preparation
- Run
./version.shoutside the sandbox when possible. It updatesapp/package.json, runs the frontend build, and refreshes generated artifacts that can require network access. - Enter the release version as
vX.Y.Zwhen prompted and confirm it. - Check the generated diff with
git status --shortandgit diff --stat. - Commit only version-preparation artifacts with:
git add <version-prep-files>
git commit -m "chore: prepare vX.Y.Z"
Do not commit release-notes-vX.Y.Z.md.
Release Notes
Create release-notes-vX.Y.Z.md in the repository root using exactly these sections:
## Features
- ...
## Bug Fixes
- ...
## Contributors
@handle
Guidelines:
- Base the notes on the verified range from the previous release tag to
HEAD. - Prefer GitHub handles for contributors when known from merged PRs or commit metadata.
- Use commit SHAs when PR numbers are not needed or not available.
- If there are no feature entries, use
- None.underFeatures. - Do not include test status unless the user explicitly asks for it.
Validation
./version.shalready runs the frontend build and Go generation.- By default, run lightweight checks such as
git diff --check. - Run broader tests only when appropriate for the release scope or when the user requests them. If the user says to skip tests, do not keep trying to run them.
- If local tests are affected by a parent Go workspace, use repo-isolated mode such as
GOWORK=offand a writableGOCACHE.
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 · 81 lines · 49 tokens per session scan A 376d42df5861
release is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 705 once invoked, about $0.0002 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
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.