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/prepare-releasenpx skills add sampleXbro/agentsmesh --skill prepare-releasegit 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.00153 | $0.03535 |
| Opus 5 | $0.00077 | $0.01767 |
| Sonnet 5 | $0.00031 | $0.00707 |
| Haiku 4.5 | $0.00015 | $0.00353 |
Grade A, and why
prepare-release 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Prepare Release
You are acting as the release engineer for agentsmesh. Your job is to get the repo into a state that is safe, honest, and ready for npm publish. Work through each phase in order. Do not mark a phase complete until you have verified it, not just assumed it.
Releases are changesets-driven — read this first
Every user-facing change ships through a changeset. Do not hand-edit package.json version or CHANGELOG.md — both are generated by changeset version and any manual edit will be silently overwritten the next time the release PR rebases. The skill exists to make sure the changeset is honest, the CI gates are green, and the publish workflow is actually wired up.
The flow:
- All gates below pass locally.
- A
.changeset/<slug>.mdfile describes the change with apatch | minor | majorbump and a user-facing summary. Commit it. - Push to
master(or merge a feature branch intomaster). publish.ymltriggers —changesets/actiondetects the pending changeset and opens a "chore: version packages" PR that bumpspackage.jsonand rewritesCHANGELOG.md.- Review the version PR — confirm the bump and the rendered CHANGELOG section match intent. Edit the changeset summary or add a new changeset (then re-push) if the rendered output is wrong; never edit
package.json/CHANGELOG.mddirectly on the version PR. - Merge the version PR →
publish.ymlruns again, sees no pending changesets, executespnpm release(pnpm build && changeset publish), and publishes to npm via npm trusted publishing. GitHub creates the Release and tag automatically.
Prerequisites in repo settings:
- Settings → Actions → General → Workflow permissions: enable "Allow GitHub Actions to create and approve pull requests".
- npm package settings → Trusted publishers: this repository +
.github/workflows/publish.ymlmust be listed for theagentsmeshpackage so OIDC can publish withoutNPM_TOKEN. - Secrets:
CODECOV_TOKENfor the coverage badge.
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 · 329 lines · 153 tokens per session scan A 317c425107b1
prepare-release is a skill published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed 3d ago), licensed MIT. It adds 153 tokens to every session and 3,535 once invoked, about $0.0008 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release-swift
Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes. Use to ship an Early Access beta or a stable release.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
release
Create a new release for grepai. Checks CI, determines version type, updates CHANGELOG and documentation, credits contributors, and creates GitHub release.