Borrowing it
Nothing to install: this file belongs to quality-screener/quality-screener-mcp-server. 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/quality-screener/quality-screener-mcp-server/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/quality-screener/quality-screener-mcp-serverWrote 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/quality-screener/quality-screener-mcp-server/release)<a href="https://agentmods.dev/commands/quality-screener/quality-screener-mcp-server/release"><img src="https://agentmods.dev/badge/commands/quality-screener/quality-screener-mcp-server/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/quality-screener/quality-screener-mcp-server/release"><img src="https://agentmods.dev/badge/commands/quality-screener/quality-screener-mcp-server/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.00020 | $0.01156 |
| Opus 5 | $0.00010 | $0.00578 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00116 |
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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a new release for qscreener-mcp. The bump type is $1 (default to patch if empty).
Critical rules
pyproject.tomlandserver.jsonversions MUST stay in sync with each other and with the git tag. The package exposes__version__viaimportlib.metadata(seeqscreener_mcp/__init__.py), and it is sent to the backend asCLIENT_ID = f"mcp/{__version__}"— a stalepyproject.tomlversion silently corrupts usage analytics.- Git tags use a
vprefix (e.g.v0.2.0); theversionfields inpyproject.tomlandserver.jsondo NOT (e.g.0.2.0). - Releases are cut directly on
main— this repo has nodevelopbranch andmainis not protected. Do not open a release PR. - Never push or tag until the version edits are committed.
- The agent never pushes to
main. Commit and tag locally, then stop and hand off — the user runs the actualgit pushthemselves. This mirrors thequality-screenerrelease process, where the agent opens the release PR but leaves merging (and thus the push tomain) to the user.
Steps
-
Sync
main. (Do this FIRST, before any edits.)git fetch origin --tagsgit switch main && git pull --ff-only origin main- Confirm the working tree is clean (
git status --porcelainreturns nothing). Abort and tell the user if it is not.
-
Determine the new version.
- Run
git tag --sort=-v:refname | head -5to find the latest tag. - If tags exist: parse the latest semver tag (strip the
vprefix) and bump according to$1:patch(default) →X.Y.(Z+1)minor→X.(Y+1).0major→(X+1).0.0
- If no tags exist (first release): do not bump. Use the version already in
pyproject.tomlas-is, and say so in the final report. - Call the new version
NEW(nov) and the tagvNEW. - Sanity check that
vNEWdoes not already exist:git rev-parse -q --verify refs/tags/vNEWmust fail.
- Run
-
Update the version manifests to
NEW:- Edit
versioninpyproject.toml([project]section). - Edit
versioninserver.json(top level). - Confirm both now read exactly
NEW:grep -n '"\?version"\? *[:=]' pyproject.toml server.json. - Skip this step if the versions already equal
NEW(first-release case).
- Edit
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 Changed · -1 lines d58f299b557b
- 10d ago First seen · 77 lines · 20 tokens per session scan A 74fcfa6a26b3
release is a command published in the GitHub repository quality-screener/quality-screener-mcp-server (0 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 1,156 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-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.