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/meteor/agent-skills/release-publishingnpx skills add meteor/agent-skills --skill release-publishinggit clone --depth 1 https://github.com/meteor/agent-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/meteor/agent-skills/release-publishing)<a href="https://agentmods.dev/skills/meteor/agent-skills/release-publishing"><img src="https://agentmods.dev/badge/skills/meteor/agent-skills/release-publishing.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.1 | $0.00032 | $0.00585 |
| Opus 5 | $0.00016 | $0.00293 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
release-publishing 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 5d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Meteor agent skills
Prepare one catalog version for Codex, Claude Code, GitHub release assets, and
direct skill installation. Read RELEASING.md before
changing release state.
Choose the release stage
| Stage | Repository visibility | Version and tag | Purpose |
|---|---|---|---|
| Working-tree test | Private or public | No new tag required | Validate local manifests and behavior. |
| Public beta | Public | X.Y.Z-beta.N and vX.Y.Z-beta.N |
Test the exact remote installation path. |
| Stable | Public | X.Y.Z and vX.Y.Z |
Publish the accepted catalog and submit it to directories. |
A GitHub repository does not need to be public for local working-tree tests.
It must be public before testing installation through
meteor/agent-skills@<tag> or submitting to public directories.
Prepare the version
Inspect the worktree first and preserve unrelated changes. Set the same global version in both plugin manifests with:
pnpm release:bump 1.0.0-beta.1
Use a stable version only after its beta has passed local and tagged remote installation tests:
pnpm release:bump 1.0.0
Do not add versions to package.json or individual SKILL.md files. The
repository tag identifies the complete catalog snapshot.
Verify
Run the checks in RELEASING.md. The tag workflow automatically rejects a tag
that does not match both manifests.
Test from the working tree before making the repository public. After pushing a beta tag, repeat the Codex, Claude Code, and individual-skill installations from that exact tag.
Publish
Treat preparation and publication as separate operations.
- A request to prepare a release authorizes local version changes and checks.
- A request to publish a release authorizes the requested commit, tag, push, and GitHub release flow.
- Marketplace submissions require the publisher account, approved listing details, and explicit authorization for that submission.
When publication is authorized, commit the verified release preparation, tag
that commit with the matching v prefix, and push the tag. The GitHub workflow
validates the version again, builds skill ZIPs, and creates the GitHub release.
Beta tags are marked as prereleases. Confirm the release succeeds before
testing remote installation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 72 lines · 32 tokens per session scan A b746c3b669b7
release-publishing is a skill published in the GitHub repository meteor/agent-skills (7 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 585 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-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…