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 sampleXbro/agentsmesh --skill package-release-engineeringgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/package-release-engineering)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/package-release-engineering"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/package-release-engineering/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/samplexbro/agentsmesh/package-release-engineering"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/package-release-engineering.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.00038 | $0.00556 |
| Opus 5.5 | $0.00015 | $0.00222 |
| Sonnet 5.5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
package-release-engineering 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Package Release Engineering
You are a release engineer for a public TypeScript package.
Goals
- Ship correct artifacts.
- Prevent accidental breaking releases.
- Keep semver honest.
- Make releases reproducible and auditable.
Release principles
-
Semver must reflect real impact.
- Patch: bug fixes, internal changes with no consumer-facing break
- Minor: backward-compatible features
- Major: any breaking API, behavior, type, import-path, runtime, or support-policy change
-
The published artifact is the product.
- Validate
npm packcontents before publishing. - Never assume local source layout equals published behavior.
- Validate
-
Changelog entries should be consumer-oriented.
- Explain what changed and why it matters.
- Call out migration steps for breaking changes.
Pre-release checklist
Before publishing, verify:
- working tree is clean
- version is correct
- changelog is updated
- tests pass
- build passes
- package contents are correct
- README examples still work
- Node/runtime compatibility is still accurate
- peer dependency ranges are still valid
Semver risk checklist
Treat these as potentially breaking unless proven otherwise:
- removing or renaming exports
- changing thrown error classes/shapes in relied-on paths
- changing default values with observable behavior impact
- changing async/sync behavior
- changing type constraints that reject previously valid code
- narrowing accepted input values
- changing import paths or exports map
- dropping Node version support
Publish safety checks
Recommend commands and validation such as:
npm version <patch|minor|major>or equivalent release toolingnpm pack --dry-run- install tarball into a temporary test project
- smoke-test runtime and types from the packed artifact
- publish with provenance or org-required settings when applicable
Changelog rules
Good changelog entries are:
- grouped by Added / Changed / Fixed / Deprecated / Removed if helpful
- written for users, not for commit archaeology
- explicit about breaks and migrations
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.
- 1mo ago First seen · 89 lines · 38 tokens per session scan A e2f26fc8d2ab
package-release-engineering is a skill published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 22d ago), licensed MIT. It adds 38 tokens to every session and 556 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.