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 naorpeled/awesome-oss-skills --skill maintainer-ci-and-release-healthgit clone --depth 1 https://github.com/naorpeled/awesome-oss-skillsWrote 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/naorpeled/awesome-oss-skills/maintainer-ci-and-release-health)<a href="https://agentmods.dev/skills/naorpeled/awesome-oss-skills/maintainer-ci-and-release-health"><img src="https://agentmods.dev/badge/skills/naorpeled/awesome-oss-skills/maintainer-ci-and-release-health/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/naorpeled/awesome-oss-skills/maintainer-ci-and-release-health"><img src="https://agentmods.dev/badge/skills/naorpeled/awesome-oss-skills/maintainer-ci-and-release-health.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.00620 |
| Opus 5 | $0.00028 | $0.00310 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
maintainer-ci-and-release-health 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer CI and release health
Use this skill for recurring checks on continuous integration, release automation, and package distribution, and for keeping agent-instruction files in sync with the conventions they are meant to enforce.
Primary inputs
.github/workflows/*.yml- release tooling such as
.goreleaser.yml,Makefile, orpackage.jsonscripts - distribution manifests: npm
package.json, Homebrew formulas, install scripts (install.js,install.sh) AGENTS.md,CLAUDE.md, or other agent-instruction files- automated code review or CI bot output (e.g. compliance or lint findings)
Instructions
Ongoing workflows
- Check that CI runs the same validation on every platform the project ships for (e.g. Linux, macOS, Windows), not just the maintainer's default environment.
- Verify pull request validation workflows and nightly/scheduled smoke tests stay aligned with the current build and release process.
- When a release changes install paths (npm, Homebrew, binaries), confirm every distribution channel was updated together, not just one.
- Cross-check automated review or compliance bot findings against the
project's documented conventions (e.g.
AGENTS.md) to confirm they are still accurate, and flag stale or contradictory rules.
One-off improvements
- Add missing cross-platform coverage to CI when a bug report is platform-specific.
- Consolidate duplicated install/build logic across distribution channels.
- Update
AGENTS.md/CLAUDE.mdwhen project conventions change so AI-assisted contributions and automated reviewers stay accurate.
Recommendations to apply
- Treat CI, release, and distribution consistency as maintainer work, on par with code review.
- Prefer fixing the root cause once (e.g. shared install logic) over patching each platform or channel separately.
- Keep agent-instruction files (
AGENTS.md,CLAUDE.md) as living documents that reflect current conventions, since automated reviewers and AI-assisted contributors rely on them. - When responding to automated review findings, verify them against the actual code before asking a contributor to act on them.
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.
- 12d ago First seen · 72 lines · 57 tokens per session scan A fecaaf630e35
maintainer-ci-and-release-health is a skill published in the GitHub repository naorpeled/awesome-oss-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 620 once invoked, about $0.0003 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-31.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
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.
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…
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.