Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sampleXbro/agentsmeshnpx agentmods add skills/samplexbro/agentsmesh/prepare-releaseWrote 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/prepare-release)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/prepare-release"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/prepare-release/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/prepare-release"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/prepare-release.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.00153 | $0.03535 |
| Opus 5.5 | $0.00061 | $0.01414 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 329 lines · 153 tokens per session scan A 317c425107b1
prepare-release is a skill published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 22d ago), licensed MIT. It adds 153 tokens to every session and 3,535 once invoked, about $0.0006 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
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.
release-notes
Drafts concise release notes from merged pull requests and conventional commits. Use when the user asks for a changelog, release notes, or a GitHub release body.
fork-and-publish-skill
Customizes an installed agent skill and ships it back upstream or as a versioned fork using qvr's edit/publish authoring loop. Use when a user wants to modify, customize, fork, release, or publish a qvr skill — e.g. "edit this skill", "publish my changes", "fork a skill to my own repo", "cut a v1.0.0 release of a…
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
deploy-check
Confirm build outputs, environment variables, release notes, and rollback steps before touching deployment configuration.