Skip to content

The plugin on toolmenu 0.28.0 - #79

Merged
niksa90 merged 2 commits into
mainfrom
claude/charming-brahmagupta-be7glj
Nov 11, 2026
Merged

niksa90 merged 2 commits into
mainfrom
claude/charming-brahmagupta-be7glj

Conversation

@niksa90

@niksa90 niksa90 commented Nov 11, 2026

Copy link
Copy Markdown
Owner

What

  • plugins/toolmenu/package.json and .claude-plugin/plugin.json: 0.28.0 (was 0.27.0).
  • plugins/toolmenu/package-lock.json, regenerated with npm install --package-lock-only --ignore-scripts: only the toolmenu entry changes, and its integrity hash is npm's.
  • CHANGELOG.md: a line under Unreleased.

Why

0.28.0 is on npm. The plugin pins a published release, and was two behind; on 0.28.0 its tools' apps/resource findings no longer call a read that failed for credentials or the network the server's.

Tests

test/mcp.test.mjs: 21 passing, including the check that the plugin pins a release this repository has published.


Generated by Claude Code

plugins/toolmenu/package.json and .claude-plugin/plugin.json to 0.28.0, now
on npm, and its lockfile (npm install --package-lock-only --ignore-scripts):
only the toolmenu entry changes, with npm's integrity hash.
@github-actions

Copy link
Copy Markdown

toolmenu

Verdict: ✓ unchanged: the same menu and the same findings. Nothing to accept. Findings against the baseline: 0 new, 0 gone, 0 changed.

toolmenu diff: toolmenu 0.28.0 → 0.28.0 (server-reported)

No breaking changes · 0 minor · 0 notices · ±0 tokens (~1,523 → ~1,523, estimate) · 6 → 6 tools

Version: suggested bump: none · not checked (set the Action's release input old..new)

No findings.

✓ 0 errors, 0 warnings, 0 info

Baseline: docs/toolmenu-menu.json as of main

toolmenu snapshot: toolmenu 0.28.0

Protocol 2026-07-28 · 6 tools · ~1,523 tokens (estimate)

1 info
Rule Finding
info write/no-dry-run · unsure 2 tools are annotated as destructive, and toolmenu found no dry_run/preview-style parameter and no preview tool for the same thing. Where a mistake is costly to undo, a dry run lets the agent see what would change while it can still back out. · snapshot_menu, check_session
→ Next: Where the effect is hard to undo, add a dry_run parameter that returns what would change without changing it. If it's cheap to undo, or a preview exists under another name, ignore this.

0 errors, 0 warnings, 1 info

Where the tokens go (estimate): the top 5 tools are 93% of the menu
Share Tool Tokens Description Schema
30% snapshot_menu ~461 ~99 ~353
26% check_session ~394 ~102 ~283
15% review_baseline ~231 ~65 ~156
12% diff_menus ~187 ~39 ~138
10% check_auth ~149 ~86 ~54
  • repeated: cwd (~37 tokens) in 4 tools, ~148 in all

A tool's schema can't $ref another tool's, so a block shared across tools is paid once per tool: only a smaller block saves tokens there.

toolmenu · token counts are estimates

@niksa90
niksa90 merged commit 18c6ebe into main Nov 11, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants