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/samplexbro/agentsmesh/package-release-engineeringnpx skills add sampleXbro/agentsmesh --skill package-release-engineeringgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWhat 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.00038 | $0.00556 |
| Opus 5 | $0.00019 | $0.00278 |
| Sonnet 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 2d 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.
- 2d 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 (24 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 556 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.