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 agentmods add skills/jrswab/axe/releasenpx skills add jrswab/axe --skill releasegit clone --depth 1 https://github.com/jrswab/axeWrote 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/jrswab/axe/release)<a href="https://agentmods.dev/skills/jrswab/axe/release"><img src="https://agentmods.dev/badge/skills/jrswab/axe/release.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.01405 |
| Opus 5 | $0.00015 | $0.00702 |
| Sonnet 5 | $0.00006 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your job is to guide the user through a full release for this project. A release includes preparing the code (version bumps, README documentation, changelog), creating an annotated git tag with a v prefix (e.g. v1.5.0), pushing it to trigger the GoReleaser GitHub Actions workflow, setting release notes, and linking the GHCR Docker image.
Rules
- Always create an annotated tag (
git tag -a), never a lightweight tag. - Tag format is
vMAJOR.MINOR.PATCHfollowing Semantic Versioning. - The changelog MUST follow Keep a Changelog 1.1.0 format.
- Valid changelog categories: Added, Changed, Deprecated, Removed, Fixed, Security.
- All version strings MUST be updated before committing. There are three locations (listed in Reference). Run version tests after bumping to catch drift.
- README.md MUST document any user-facing changes — new config fields, CLI flags, behavior changes, exit codes.
- DO NOT push to master until the user confirms.
- DO NOT push the tag until the user confirms.
- DO NOT skip asking the user for the version number, tag annotation message, and changelog review.
Steps
-
Gather context
- Check the current branch and ensure it is clean (
git status). - List existing tags (
git tag --sort=-v:refname) to determine the next version. - Collect the commit log since the last tag (or all commits if this is the first release).
- Check the current branch and ensure it is clean (
-
Ask the user
- What version number to use.
- What the annotated tag message should say.
- Whether the auto-generated changelog looks correct or needs edits.
-
Categorize commits into Keep a Changelog sections:
Added— new features and capabilities.Changed— changes to existing functionality.Deprecated— features marked for removal.Removed— features that were removed.Fixed— bug fixes.Security— vulnerability fixes.- Exclude commits prefixed with
docs:,test:,ci:, or merge commits.
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.
- 4d ago First seen · 108 lines · 30 tokens per session scan A 72f8f6f9a520
release is a skill published in the GitHub repository jrswab/axe (836 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,405 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
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes…
make-release
Prepare and publish a new release for the wiswa-mcp project.
smbcloud-cli-release
Use when building, packaging, or releasing smbCloud CLI binaries through npm, PyPI, or GitHub Actions CI/CD. Covers the Rust binary release source of truth, the npm wrapper and platform packages, the PyPI maturin package under pypi/, local publishing with uv tool install maturin, and fixes to…
smbcloud-docs-release
Use when building, generating, or releasing the smbCloud documentation site (website/, Nextra + Next.js) — the developer-docs generation pipeline that reads the sibling docs/ tree, the nextjs-ssr deploy via smb deploy, and the public-repo content boundary.
quality-engineer-manager
Quality Engineer Manager skill for orchestrating release validation, beta testing coordination, feedback analysis, and release sign-off decisions.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.