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/n-n-code/n-n-code-skills/project-release-maintainernpx skills add n-n-code/n-n-code-skills --skill project-release-maintainergit clone --depth 1 https://github.com/n-n-code/n-n-code-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/n-n-code/n-n-code-skills/project-release-maintainer)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/project-release-maintainer"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/project-release-maintainer.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.00041 | $0.00548 |
| Opus 5 | $0.00020 | $0.00274 |
| Sonnet 5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
project-release-maintainer 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 today.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Release Maintainer
This is a composable project overlay. Add matching implementation guidance when
source, build, or automation code changes. Compose with documenter when the
main artifact is durable release, install, or contributor documentation.
For review or planning, inspect and report without changing package contents, manifests, notices, or release state. Apply the workflow as edit instructions only when the user asks for those changes.
When to use
The change affects the shipped or published contract: package contents, install rules, release automation, shipped assets, license and notice files, release checklists, or documentation that must match those artifacts.
Not for
Use documenter alone for content-only edits that do not require reconciliation
with shipped artifacts. For internal code changes with no release impact, use
the matching principle skill and add project-core-dev only when repository-
specific completion evidence is not concrete. Use project-config-and-tests
for config contracts. Use project-vendor-boundary as primary for vendored
source ownership, and compose both overlays when a vendor change also alters
shipped metadata.
Workflow
- Inventory the existing release contract from package manifests, install rules, shipped assets, release automation, license and notice files, checklists, and public documentation. Identify the source of truth before editing.
- Trace the requested change across only the affected artifacts. Keep package contents, install behavior, public commands, examples, and release notes mutually consistent.
- Use the repo's existing dry-run, package-listing, hygiene, and verification commands. When install behavior changes, validate in a temporary install tree and clean it up; smoke-test the installed artifact when practical.
- Inspect the produced package or staged tree rather than inferring contents from build configuration alone. Report unavailable signing, platform, or publication checks instead of implying they passed.
- Keep documentation concise and grounded in the shipped build. Do not invent CI, packaging, signing, publishing, or release workflows that the repo does not contain or the user did not request.
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.
- today Changed · +4 lines 97d9f5e5f1bc
- 5d ago First seen · 52 lines · 41 tokens per session scan A 44a7f39eb4bd
project-release-maintainer is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 548 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-31.
Other skills, from other repositories
release-note
Changelog and release notes.
release-skills
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release"…
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
git-workflow
Git 工作流专家。规范化版本控制，确保提交历史清晰可追溯。支持 Conventional Commits 规范、Pull Request 最佳实践、分支管理策略和自动化工作流。.
git-publish-release
当用户明确要求"发布项目到 GitHub"、"创建 GitHub Release"或"生成 Release Notes"时使用。智能分析 tag 间历史变化并生成专业的 Release Notes；明确发布/创建请求时自动创建 GitHub Release，单独的 notes/历史总结请求仅生成预览，除非用户随后确认发布。支持首次发布、常规版本、预发布版本（alpha/beta/rc），自动识别 prerelease 标记。.