Borrowing it
Nothing to install: this file belongs to Ninjabeam20/SportIQ-MCP. 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/Ninjabeam20/SportIQ-MCP/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/Ninjabeam20/SportIQ-MCPWrote 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/ninjabeam20/sportiq-mcp/release)<a href="https://agentmods.dev/commands/ninjabeam20/sportiq-mcp/release"><img src="https://agentmods.dev/badge/commands/ninjabeam20/sportiq-mcp/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/ninjabeam20/sportiq-mcp/release"><img src="https://agentmods.dev/badge/commands/ninjabeam20/sportiq-mcp/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.00018 | $0.00333 |
| Opus 5 | $0.00009 | $0.00167 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $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 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
/project:release $ARGUMENTS
Cut a release. Argument is the semver bump kind.
Workflow
- Read
pyproject.tomlcurrent version. - Compute new version per the bump kind.
- Show the user the new version + the changelog (from
git logsince the last tag). - STOP. Wait for explicit "yes". Per CLAUDE.md Rule #7, publishing is irreversible.
- After approval:
uv run pytest(must pass).uv run ruff check .(must pass).- Bump version in
pyproject.toml. git commit -m "release: vX.Y.Z".git tag vX.Y.Z.git push && git push --tags(only after explicit confirmation).uv build.- The
publish.ymlworkflow handlesuv publishon tag push (added in Phase 5).
- Append to
docs/log.md:## [YYYY-MM-DD] release | vX.Y.Z to PyPI. {tools added | bugfixes | breaking changes}. - End with Rule #8 format.
Hard rules
- NEVER publish without
uv run pytestpassing. - NEVER force-push tags.
- NEVER bump version in a branch other than
main.
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 · 33 lines · 18 tokens per session scan A ba1f74e7a312
release is a command published in the GitHub repository Ninjabeam20/SportIQ-MCP (10 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 333 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
release
Prepare and execute a Python package release with verification steps.
uv-publish
A command for publishing a Python package with uv, a Python tool for managing projects and dependencies, to PyPI, the main public package repository.
create_project
Create a new project from template with uv and Git initialization.
cargo-publish
Command "cargo-publish" from olorehq/olore, covering cargo-publish(1), name, synopsis, description and options.
cargo-yank
Command "cargo-yank" from olorehq/olore, covering cargo-yank(1), name, synopsis, description and how yank works.
release
Automates the release preparation and CI/CD handoff process.