Release and continuous-integration guidance for the quota-axi project. It covers automated version changes, changelog creation, npm publishing, contribution checks, and lockfile rules.

Use it when configuring release workflows, conventional commit messages, release-please, npm publishing, generated-file guards, or contribution gates.

It keeps releases consistent and prevents contributors from manually changing files that automation owns. Continuous integration, or CI, runs checks automatically when code changes.

release-ci — Skill for Claude Code by kunchenguid/quota-axi

Install

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.

Any agent

npx skills add kunchenguid/quota-axi --skill release-ci

Clone the repo

git clone --depth 1 https://github.com/kunchenguid/quota-axi

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kunchenguid/quota-axi/release-ci/github.svg)](https://agentmods.dev/skills/kunchenguid/quota-axi/release-ci)

Your own site

<a href="https://agentmods.dev/skills/kunchenguid/quota-axi/release-ci"><img src="https://agentmods.dev/badge/skills/kunchenguid/quota-axi/release-ci/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kunchenguid/quota-axi/release-ci"><img src="https://agentmods.dev/badge/skills/kunchenguid/quota-axi/release-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 873 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00026	$0.00873
Opus 5.5	$0.00010	$0.00349
Sonnet 5.5	$0.00005	$0.00175
Haiku 4.5	$0.00003	$0.00087

Measured 13d ago against content hash cd911bba672b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-ci 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 13d 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.

skills/release-ci/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Automation, CI & Contribution Gate

This document describes the automated release pipeline, CI workflow constraints, contribution gate architecture, and repository maintenance rules in quota-axi.

Release Process & Automation

Conventional Commits: Releases are driven by conventional commit messages (feat:, fix:, chore:, etc.) merged into main.
Release Please:
- Automatically manages version bumps, changelog generation, and release PRs.
- .release-please-manifest.json was primed at 0.1.0 (the version published manually before release-please integration); release-please updates it with each release.
- release-please-config.json locks bootstrap-sha to 9f5dc949c50ab8ac0a441be777e1c3693ee0b612 (the commit producing the published 0.1.0 package). Never alter this SHA unless correcting the published baseline.
- Never Hand-Edit Generated Files: Do not manually edit CHANGELOG.md or .release-please-manifest.json. A guard workflow (.github/workflows/guard-generated-files.yml) automatically rejects PRs that touch them.
npm Publishing:
- Merging the release PR triggers .github/workflows/release-please.yml to publish to npm.
- Uses npm's OIDC trusted-publisher flow (id-token: write + --provenance) without stored token secrets.
- Publishing steps are gated only on steps.release.outputs.release_created; the workflow has no repository guard. The binding to this package comes from npm's trusted-publisher OIDC configuration.
Skill Generation:
- skills/quota-axi/SKILL.md is generated from src/skill.ts.
- Regenerate via pnpm run build:skill rather than editing directly. CI validates parity via pnpm run build:skill -- --check.

CI Workflows & Exclusion Rules

Release Output Set Exclusions:
- Every pull_request workflow (ci.yml, guard-generated-files.yml) must include a paths-ignore filter covering the release-please output set (.release-please-manifest.json, CHANGELOG.md, package.json).
Gate Check Exception:
- The single deliberate exception to the paths-ignore rule is .github/workflows/no-mistakes-required.yml.
- The gate check verdict is a function of the pull request body, not the changed files. Adding a path filter would drop the gate on PRs that still require attestation.
- Both sides of this rule are guarded by test/release-ci-exclusions.test.ts.

Read the full file on GitHub · 63 lines

Changes

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.

13d ago First seen · 63 lines · 26 tokens per session scan A cd911bba672b

Subscribe to this mod's changes

release-ci is a skill published in the GitHub repository kunchenguid/quota-axi (155 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 873 once invoked, about $0.0001 per session on Opus 5.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-10-05.

CI and CD DevOps and cloud Git and workflow Releases

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

agent-github-modes

Agent skill for github-modes - invoke with $agent-github-modes.

ruvnet/ruflo · 21 tokens

factory-ship

Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.

BuilderIO/skills · 28 tokens

releasepr

Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.

compozy/compozy · 53 tokens

gitlab-devops

GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…

automateyournetwork/netclaw · 67 tokens

seed-snapshot-release

An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.

daangn/seed-design · 19 tokens