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 commands/sealjay/mcp-whatsapp/releasegit clone --depth 1 https://github.com/Sealjay/mcp-whatsappWrote 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/commands/sealjay/mcp-whatsapp/release)<a href="https://agentmods.dev/commands/sealjay/mcp-whatsapp/release"><img src="https://agentmods.dev/badge/commands/sealjay/mcp-whatsapp/release.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 | $0.00000 | $0.00328 |
| Opus 5 | $0.00000 | $0.00164 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
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 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.
What it actually says
Release a new version. Determines the bump type from recent commits, runs the full checklist, tags, pushes, and creates a GitHub release.
Steps
-
Determine bump type from commits since the last tag:
- If
$ARGUMENTSismajor,minor, orpatch, use that directly. - Otherwise, inspect
git log $(git describe --tags --abbrev=0)..HEAD --oneline:- Any commit mentioning "breaking" or "BREAKING CHANGE" -> major
- Any commit with
feat:prefix or new tool registrations -> minor - Otherwise -> patch
- If
-
Calculate next version: parse the latest tag (
git describe --tags --abbrev=0), increment the appropriate component, reset lower components to 0. -
Pre-flight checks (abort on failure):
git statusmust show a clean working tree (no uncommitted changes)git branch --show-currentmust bemainmake lintmust passmake testmust pass
-
Tag and release:
git tag v<MAJOR>.<MINOR>.<PATCH>git push origin maingit push origin v<MAJOR>.<MINOR>.<PATCH>gh release create v<MAJOR>.<MINOR>.<PATCH> --generate-notes
-
Report: print the new version, release URL, and a one-line summary.
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 · 29 lines · 0 tokens per session scan A 8cef1f08f767
release is a command published in the GitHub repository Sealjay/mcp-whatsapp (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 328 tokens. 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 commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
release
Release a new version of rubyllm-agents to RubyGems and GitHub.
changeset
../../.mastracode/commands/changeset.md.
changelog
Analyze commits and generate formatted changelog entry for a version.
release-check
Comprehensive pre-flight check for release readiness without making any changes.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.