Borrowing it
Nothing to install: this file belongs to respawn-llc/tool-filter-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/respawn-llc/tool-filter-mcp/master/.claude/commands/publish.mdgit clone --depth 1 https://github.com/respawn-llc/tool-filter-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/respawn-llc/tool-filter-mcp/publish)<a href="https://agentmods.dev/commands/respawn-llc/tool-filter-mcp/publish"><img src="https://agentmods.dev/badge/commands/respawn-llc/tool-filter-mcp/publish.svg" alt="Measured on agentmods" 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.00015 | $0.00541 |
| Opus 5 | $0.00008 | $0.00270 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
publish 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 8d 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
Release Process
Execute the following steps to publish a new version:
1. Switch to master branch (if needed)
git checkout master && git pull
2. Bump version
Choose the appropriate version bump:
-
Patch (0.2.0 → 0.2.1): Bug fixes, minor changes
npm version patch -m "chore: bump version to %s" -
Minor (0.2.0 → 0.3.0): New features, backwards compatible
npm version minor -m "chore: bump version to %s" -
Major (0.2.0 → 1.0.0): Breaking changes
npm version major -m "chore: bump version to %s"
This updates package.json and creates a git tag automatically.
3. Push version commit and tags
git push && git push --tags
4. Publish to npm
Ask the user to provide the OTP code or to run the command:
npm publish --otp=<6-digit-code-from-authenticator>
The prepublishOnly script runs npm run build automatically.
5. Create GitHub release
gh release create v<VERSION> --title "v<VERSION> - <Title>" --notes "<Release notes>"
Example:
gh release create v0.2.0 --title "v0.2.0 - HTTP Header Pass-Through" --notes "## Features
- Add HTTP header pass-through for authentication
- Environment variable expansion support
**Full Changelog**: https://github.com/respawn-llc/tool-filter-mcp/compare/v0.1.0...v0.2.0"
Verification
After publishing:
- Check npm: https://www.npmjs.com/package/@respawn-app/tool-filter-mcp
- Check GitHub releases: https://github.com/respawn-llc/tool-filter-mcp/releases
- Test installation:
npx @respawn-app/tool-filter-mcp@latest --help
Requirements
- npm authentication configured (
npm login) - npm 2FA enabled (OTP required)
- GitHub CLI authenticated (
gh auth login) - Write access to the repository
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.
- 8d ago First seen · 83 lines · 15 tokens per session scan A d7db9bbf7ed0
publish is a command published in the GitHub repository respawn-llc/tool-filter-mcp (36 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 541 once invoked, about $0.0001 per session on Opus 5. 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
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.
doc-changelog
Generation and maintenance of the project changelog.