Borrowing it
Nothing to install: this file belongs to receptron/mulmoclaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/receptron/mulmoclaude/main/.claude/skills/release-app/SKILL.mdgit clone --depth 1 https://github.com/receptron/mulmoclaudeWrote 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/receptron/mulmoclaude/release-app)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/release-app"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/release-app/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/receptron/mulmoclaude/release-app"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/release-app.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.00016 | $0.00916 |
| Opus 5 | $0.00008 | $0.00458 |
| Sonnet 5 | $0.00003 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
release-app 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 9d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MulmoClaude App Release
This skill creates a GitHub release for the MulmoClaude app (not individual npm packages).
IMPORTANT: App releases use v prefix tags (v0.2.0). Package releases use bare tags (@mulmobridge/[email protected]). Never mix them.
Pre-release Checks
- Confirm branch: Must be on
mainwith a clean working treegit status git branch - Get current version and last release:
jq -r .version package.json gh release list --repo receptron/mulmoclaude --limit 5 - Ask the user: What version? (patch / minor / major) and confirm
Steps
-
Get today's date (MUST run
date, never guess):date +%Y-%m-%d -
Count changes since last app release:
# Find the last vX.Y.Z tag (not package tags) LAST_TAG=$(git tag -l 'v*' --sort=-v:refname | head -1) git log --oneline "$LAST_TAG"..HEAD --no-merges | wc -l git log --oneline "$LAST_TAG"..HEAD --no-merges | head -30 -
Update
docs/CHANGELOG.md:- Add a new
## [X.Y.Z] - YYYY-MM-DDsection at the top (below the header) - Follow Keep a Changelog format
- Sections:
Highlights,Added,Changed,Fixed,Security,Breaking Changes(only if applicable) - Write concise bullet points — focus on user-visible changes
- If a previous release entry is misattributed (e.g., a package release using an app version), annotate it with "(package release)"
- Add a new
-
Update
package.jsonversion:# Edit package.json version field to the new version -
Commit version bump (add files individually):
git add docs/CHANGELOG.md package.json git commit -m "chore: bump version to X.Y.Z + update CHANGELOG" -
Create git tag (WITH
vprefix for app releases):git tag vX.Y.Z git push origin main --tags -
Create GitHub release:
gh release create vX.Y.Z --repo receptron/mulmoclaude \ --title "vX.Y.Z — Short Description" \ --notes "$(cat <<'EOF' ## Highlights ### Feature 1 Description... ### Feature 2 Description... ## Breaking Changes - (if any) ## Full Changelog See [CHANGELOG.md](https://github.com/receptron/mulmoclaude/blob/main/docs/CHANGELOG.md#xyz---yyyy-mm-dd) for the complete list. EOF )"
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.
- 9d ago First seen · 105 lines · 16 tokens per session scan A 0bd7972e5fd8
release-app is a skill published in the GitHub repository receptron/mulmoclaude (346 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 916 once invoked, about $0.0001 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
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.