Borrowing it
Nothing to install: this file belongs to khuynh22/mcp-wireshark. 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/khuynh22/mcp-wireshark/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/khuynh22/mcp-wiresharkWrote 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/khuynh22/mcp-wireshark/release)<a href="https://agentmods.dev/commands/khuynh22/mcp-wireshark/release"><img src="https://agentmods.dev/badge/commands/khuynh22/mcp-wireshark/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/commands/khuynh22/mcp-wireshark/release"><img src="https://agentmods.dev/badge/commands/khuynh22/mcp-wireshark/release.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 10d 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
Trigger a release for mcp-wireshark.
The CI handles everything automatically — no manual version bumping needed.
How it works
-
The PR must have exactly one of these labels before merging:
release:patch→ 0.1.x (bug fixes, security fixes, no new tools)release:minor→ 0.x.0 (new tools, new optional params, backwards-compatible)release:major→ x.0.0 (removed tools, changed required params, breaking changes)
-
When the PR is merged to
main,auto-release.ymlautomatically:- Bumps the version in
pyproject.toml,src/mcp_wireshark/__init__.py, andmcp.json - Commits the bump as
chore: bump version to X.Y.Z - Creates and pushes a
vX.Y.Zgit tag - Builds and publishes to PyPI
- Creates a GitHub Release with auto-generated release notes
- Sends an email notification
- Bumps the version in
What to tell the user
Ask: "Does the current PR need a release? If so, which type: patch, minor, or major?"
Then tell them:
- Add the appropriate
release:patch / release:minor / release:majorlabel to the PR on GitHub before merging - After merging, the CI takes 2–3 minutes and handles everything
- They can watch progress at: https://github.com/khuynh22/mcp-wireshark/actions
If no label is added
The PR merges cleanly with no version bump. The change ships in the next release whenever they add a label to a future PR.
Manual fallback
If auto-release failed, use the "Manual Release" workflow on GitHub Actions — it takes a version string and publishes that exact tag to PyPI.
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.
- 10d ago First seen · 36 lines · 0 tokens per session scan A eac4641c568b
release is a command published in the GitHub repository khuynh22/mcp-wireshark (57 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 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-30.
Other commands, from other repositories
ship
Complete PR workflow from commit to production with validation.
work-flow-release
Complete workflow to prepare and publish a release.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
ci
Run CI validation, create PRs, and merge on green.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
ci
Trigger GitHub Actions CI/CD builds, sign, publish, or check CI status.