Repository navigation
Conversation
`prowl.chat/mcp/skill.md` serves 444 tools; this package said 448 in
`src/config.js`, its npm description and its README. The repository's own
`npm run check:tools` says so outright:
FAIL: https://prowl.chat/mcp/skill.md serves 444 tools, and these files
say otherwise: src/config.js: 448, package.json: 448, README.md: 448
It was not caught because CI runs on push and this number drifts when the
SERVER moves, not when the repository does — the last CI run here was
2026-08-16. So the workflow now also runs weekly: a quiet repository has to
be able to notice.
`AGENTS.md` is the agent-facing entry point the agent-plugins.org convention
expects at the root; `CONTRIBUTING.md` stays the human version and wins where
the two ever disagree.
Verified: `npm test` 80 passed / 0 failed in a clean HOME, `npm run
check:tools` green against the live server.
Note for whoever runs the suite locally: `test/_mock.js::runClean` clears the
four PROWL_* env vars but not `~/.prowl/prowl_mcp_token`, which
`src/config.js:28` also reads — so on a machine that has that file the two
`auth status with no key` tests authenticate for real, reach the network and
fail. Green in CI and in a clean HOME; left alone here because it is not this
change's subject.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this fixes
prowl.chat/mcp/skill.mdserves 444 tools. This package said 448 in three places, and its own checker says so:That number is on npm and in the README, so it is what a stranger reads.
Why the existing guard did not catch it
check:toolsis wired into CI and works — it produced the message above on the first run. It just never ran: CI triggers on push, and this number drifts when the server moves, not when the repository does. The last CI run here was 2026-08-16, and the count went 448 → 444 after that.So the workflow now also runs on a weekly schedule. A quiet repository has to be able to notice; otherwise the same row comes back every time somebody deregisters a tool.
AGENTS.md
The agent-facing entry point the agent-plugins.org convention expects at the repository root.
CONTRIBUTING.mdstays the human version and wins where the two ever disagree — the new file says so in its first paragraph.Verification
npm test— 80 passed, 0 failed in a cleanHOMEnpm run check:tools—OK: … serves 444 tools; 3 file(s) agree.One note that is not part of this change
test/_mock.js::runCleanclears the fourPROWL_*env vars but not~/.prowl/prowl_mcp_token, whichsrc/config.js:28also reads. On a machine that has that file, the twoauth status with no keytests authenticate for real, reach the network (~4.3 s each) and fail — in a suite whose contract is "offline by design". Green in CI and in a cleanHOME, so it is left alone here and reported rather than folded in.🤖 Generated with Claude Code