Borrowing it
Nothing to install: this file belongs to yoshiko-pg/o3-search-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/yoshiko-pg/o3-search-mcp/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/yoshiko-pg/o3-search-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/yoshiko-pg/o3-search-mcp/release)<a href="https://agentmods.dev/commands/yoshiko-pg/o3-search-mcp/release"><img src="https://agentmods.dev/badge/commands/yoshiko-pg/o3-search-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/yoshiko-pg/o3-search-mcp/release"><img src="https://agentmods.dev/badge/commands/yoshiko-pg/o3-search-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.00000 | $0.00311 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 9d 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
Update CHANGELOG.md with all changes from the latest tag to current commit.
First, run the script to get commit information:
./scripts/get-changes-since-tag.sh
Use the script output to categorize changes:
Addedfor new features.Changedfor changes in existing functionality.Deprecatedfor soon-to-be removed features.Removedfor now removed features.Fixedfor any bug fixes.Securityin case of vulnerabilities.Thanksfor contributors mention with GitHub username and PR number
When processing commits:
- Use the GitHub username from script output (not git commit author names)
- Only include contributors in Thanks section (exclude yoshiko-pg as that's the maintainer)
- Include PR numbers when available
- Use commit subject and body to properly categorize changes
Then inform the user in Japanese about the added content and ask for confirmation with say command.
If confirmed OK:
- npm version --no-git-tag-version patch
- Create a version section in CHANGELOG.md and move Unreleased section content there
- Update the version links at the bottom of CHANGELOG.md (add new version links and update Unreleased link)
- Commit CHANGELOG.md
- create current version git tag
- git push origin main --tags
- create release on github with CHANGELOG.md target version section text (to origin)
Then ask the user to run npm publish with say command. (Do not execute npm publish yourself)
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.
- 9d ago First seen · 39 lines · 0 tokens per session scan A 0fc709ff0d23
release is a command published in the GitHub repository yoshiko-pg/o3-search-mcp (288 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 311 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
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
fire-update
Check for and apply plugin updates from GitHub repository.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
release-train
Autonomous multi-PR release train — plan stacked single-concern PRs, open each on its own branch, monitor CI, rebase on conflicts, and ship in dependency order while you sleep. Driven by report.html horizon item 'Autonomous Multi-PR Release Trains'.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.