Repository navigation
Releases
Releases · niksa90/toolmenu
v0.29.0
What's Changed
- Retire description/late-instruction by @niksa90 in #82
- 0.29.0: instructions/unknown-name, spec/discover-refused, config rule-id warning, auth login and diff notes by @niksa90 in #83
Full Changelog: v0.28.1...v0.29.0
v0.28.1
v0.28.0
What's Changed
- snapshot --read-resources: read each listed resource by @niksa90 in #75
- apps/resource: run failures are info; the weekly bench reads resources by @niksa90 in #76
- 0.28.0: version, changelog, Action pins; the PR comment checks toolmenu mcp by @niksa90 in #77
Full Changelog: v0.27.1...v0.28.0
v0.27.1
What's Changed
- README as the pitch, the reference in docs/; two more MCP tools; the plugin on 0.27.0 by @niksa90 in #73
- 0.27.1: version, changelog, Action pins by @niksa90 in #74
Full Changelog: v0.27.0...v0.27.1
v0.27.0
v0.26.0
Security
From a security audit of the repository.
auth loginopens onlyhttpslogin addresses (orhttpto this machine).
The address comes from the server's OAuth metadata, and the browser opener does
whatever its scheme says: a hostile server could havexdg-open,openor
rundll32open afile:,smb:or app link, which on Windows can start a program.
It's refused before anything is opened or printed.toolmenu mcp: honest annotations,save_asinsidecwd.snapshot_menuand
check_sessionrun the command they're given, but were annotated
destructiveHint: false, so a client that auto-approves non-destructive tools would
let a prompt-injected agent run anything. They'redestructiveHint: truenow.
save_aswrites only insidecwd(symlinks followed): a new file, or an existing
menu file, never a shell profile or a source file.- Reports show a server's text; they never act on it. Tool names, descriptions,
serverInfoand error text went into reports as sent. In a terminal, escape
sequences could change the title, clear the screen or fake links, and a newline
could forge a finding or a::error::line in a CI log. In markdown (the Action's
PR comment) a backtick ended the code span, and images, links, @mentions and
#references rendered, posted by github-actions. Now control, invisible and
text-direction characters are shown as escapes (\u001b,\n), markdown is escaped
around toolmenu's owncode, and every write to stdout and stderr goes through the
same escaping. JSON output stays the same JSON. The menu file keeps the exact bytes. - The Action's PR comment can't be taken over. It edited the first comment with
its marker, whoever wrote it; now only one its own token wrote. - The Action keeps PR text out of its arguments and its markdown:
--releaseis
one argument (apackage.jsonversion with spaces added arguments), and error
output goes in a code block its backticks can't close. scanfills${VAR}only from variables you name with--allow-env(or'*').
A config decides where each value goes, a URL included, so scanning someone else's
.mcp.jsoncould send any secret in your environment to their server.- Credentials off the command line.
TOOLMENU_ARGS(a JSON array of options and
their values) keeps--header,--envand--client-secretvalues out ofps,
where every user of the machine can read them; the Action passes itsheadersand
envthat way (to an olderversionstill as arguments, with a warning). - Release and CI workflows: least-privilege tokens, every action pinned to a
commit (Dependabot keeps them current), and the npm package built in a job apart
from the tests and published from a job that runs no dependency, with npm's trusted
publishing: no long-lived npm token anymore.toolmenu init
pins the actions it writes the same way. - Smaller: a menu file,
toolmenu.config.jsonor scan list that isn't JSON is
reported without quoting it; JUnit output escapes characters a terminal acts on;
historyuses only semver-shaped registry versions; macOS runners (bash 3.2) get
their SARIF files.
Breaking
scan: a config that uses${VAR}needs--allow-env VAR(or--allow-env '*'
for the old behaviour). The entry says which.toolmenu mcp:save_asoutsidecwd, or over a file that isn't a menu, is an
error. The release-check skill keeps its baseline inside the worktree.snapshotexits 1 on a server whose tool names hold control, invisible or
text-direction characters (spec/tool-name, below).
Also
spec/tool-name: a tool name outside the format the spec recommends from
2025-11-25 (1 to 128 ofA-Z a-z 0-9 _ - .) is a warning (info on older
protocols), and an error when it hides characters.- An HTML report.
--html <path>writes the run ofsnapshot,difforsession
as one self-contained page beside the usual report: stat cards (errors, warnings,
tools, tokens; breaking changes and the suggested bump fordiff), the menu as a
table in server order with each tool's share of the tokens, and the findings with
their next steps.diffshows each tool before and after;sessionhas a row per
step with the menu after it, marking tools inserted, appended or edited, and links
each step to its findings. No script and nothing fetched, so it opens offline from a
CI artifact; light and dark follow the viewer. The design follows the Board UI
design system, in the logo's colours. - Library:
sessiontakesonStepMenu(the menu after each step, with what the step
inserted, appended, moved, edited or removed;stepMenuandStepToolare
exported), kept out of the result so the JSON output is unchanged. New
comparedTools(before, after, ignore)returns the toolsdiffMenuscompares (after
the ignore globs, with their served positions) and which were added, removed and
renamed;diffMenususes it too.
v0.25.2
v0.25.1
- In the MCP Registry.
server.jsonlists toolmenu's MCP server as
io.github.niksa90/toolmenu, andpackage.jsongains the matchingmcpName, which
is how the registry checks that the npm package is this server's. The release
workflow publishes the entry after npm, signed in with GitHub's OIDC token. - The npm page shows the logo and the Glama badge
0.25.0
- A README badge.
snapshot --badge <path>writes a shields.io endpoint file
(toolmenu | 12 tools · ~4.1K tokens · 2 warnings, red with errors, yellow with
warnings) and prints the README line, which reads it from GitHub on the default
branch. Committed with the baseline, it changes when the baseline does. toolmenu's
README shows its own MCP server's. - SARIF output, for GitHub code scanning.
--sarif <path>writes the findings
ofsnapshot,difforsessionas SARIF 2.1.0 beside the usual report;
--format sarifprints it instead. Each result points at the menu file, at the line
of the tool it's about (--sarif-menunames the committed one when the menu was
written elsewhere), with a fingerprint from its rule and tool (and which of that
rule's findings on the tool it is) so alerts track across runs. The Action's newsarifinput writessnapshot.sarif,diff.sarifand
session.sarifinto a folder forgithub/codeql-action/upload-sarif. - Plugin: two more skills, and evals.
release-check(before tagging or
publishing: what changed since the last release, what breaks clients, the bump it
needs) andsetup-ci(adds toolmenu to CI withtoolmenu init).check-mcp-menu
names more of the moments it's for (a rename, a description edit, an agent picking
the wrong tool) and falls back to the CLI without the MCP tools.
plugins/toolmenu/evals/has seven cases forclaude plugin eval: each skill fires
on its own prompts (3 of 3 runs, 0 of 3 without the plugin), none fires on unrelated
work, andsetup-cigives the rightinitcommand for a scaffolded project.