Borrowing it
Nothing to install: this file belongs to julianoczkowski/notebooklm-mcp-2026. 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/julianoczkowski/notebooklm-mcp-2026/master/.claude/commands/release.mdgit clone --depth 1 https://github.com/julianoczkowski/notebooklm-mcp-2026Wrote 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/julianoczkowski/notebooklm-mcp-2026/release)<a href="https://agentmods.dev/commands/julianoczkowski/notebooklm-mcp-2026/release"><img src="https://agentmods.dev/badge/commands/julianoczkowski/notebooklm-mcp-2026/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/julianoczkowski/notebooklm-mcp-2026/release"><img src="https://agentmods.dev/badge/commands/julianoczkowski/notebooklm-mcp-2026/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.00615 |
| Opus 5 | $0.00000 | $0.00308 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new version of notebooklm-mcp-2026 to PyPI.
Instructions
You are automating the release process for the notebooklm-mcp-2026 Python package. Follow these steps in order. If any step fails, stop immediately and report the error — do NOT proceed to later steps.
Step 1: Pre-flight checks
Run these in parallel:
ruff check src/ tests/— lint must passpytest -v --tb=short— all tests must passgit status— working tree must be clean (no uncommitted changes). If there are uncommitted changes, stop and ask the user to commit or stash them first.gh auth status— GitHub CLI must be authenticated
If any check fails, stop and report the issue.
Step 2: Determine version
Read the current version from pyproject.toml (the version field under [project]).
Ask the user what kind of bump they want:
- patch (e.g. 0.1.2 → 0.1.3) — bug fixes, small changes
- minor (e.g. 0.1.2 → 0.2.0) — new features, non-breaking
- major (e.g. 0.1.2 → 1.0.0) — breaking changes
Compute the new version number. Show the user: Current: X.Y.Z → New: A.B.C and confirm before proceeding.
Step 3: Bump version
Edit pyproject.toml and change the version field to the new version.
Step 4: Commit and tag
git add pyproject.toml
git commit -m "Release v{NEW_VERSION}"
git tag v{NEW_VERSION}
Step 5: Push
git push origin master
git push origin v{NEW_VERSION}
Note: The main branch is master. Push both the commit and the tag.
Step 6: Create GitHub release
gh release create v{NEW_VERSION} --title "v{NEW_VERSION}" --generate-notes
Step 7: Watch pipeline
Run gh run watch to monitor the CI + publish pipeline. Wait for it to complete.
If the pipeline fails:
- Report the failure
- Do NOT delete the tag or release automatically — ask the user what they want to do
Step 8: Verify
Run gh run list --limit 3 to confirm the release workflow succeeded.
Tell the user:
- The new version
v{NEW_VERSION}has been released - PyPI page: https://pypi.org/project/notebooklm-mcp-2026/{NEW_VERSION}/
- GitHub release: the URL from
gh release view v{NEW_VERSION} --json url
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 · 71 lines · 0 tokens per session scan A 73a231d36e84
release is a command published in the GitHub repository julianoczkowski/notebooklm-mcp-2026 (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 615 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
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
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.
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.