Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/sergiobayona/vector_mcp/releasegit clone --depth 1 https://github.com/sergiobayona/vector_mcpWhat 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 | $0.00000 | $0.01543 |
| Opus 5 | $0.00000 | $0.00772 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00154 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.
Overview
This command guides you through the complete release process for the VectorMCP gem, ensuring all steps are followed correctly and the release is done safely from a clean state.
Steps
1. Pre-release Checks
First, let's verify we're in a clean state and on the main branch:
!git status --porcelain
!git branch --show-current
If there are uncommitted changes, you should commit or stash them first.
If you're not on the main branch, switch to it: git checkout main
2. Update from Remote
Ensure we have the latest changes from the remote repository:
!git pull origin main
3. Version Comparison Check
CRITICAL: Compare local version against published gem version to prevent conflicts:
# Check current local version
!grep -n "VERSION" lib/vector_mcp/version.rb
# Check latest published version on RubyGems
!gem list vector_mcp --remote --exact
# Alternative: Check specific version info
!gem query --remote --exact --name vector_mcp
Version Analysis:
- If local version matches published version → Need to bump version
- If local version is newer → Ready for release (verify changelog)
- If local version is older → Update to appropriate new version
4. Documentation Review
CRITICAL: Verify README.md reflects all new features since last release:
# Check commits since last published version tag
!git log --oneline $(git describe --tags --abbrev=0)..HEAD
# Review README.md for feature completeness
!grep -n "## Features\|### Features\|## What's New" README.md
README.md Review Checklist:
- All new features from commits are documented
- Installation instructions are current
- Usage examples reflect new capabilities
- API documentation matches current version
- Breaking changes are clearly noted
- Links and references are working
Common README.md Sections to Update:
- Features list
- Installation/Setup instructions
- Usage examples and code samples
- API documentation
- Breaking changes section
- Known issues or limitations
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.
- 2d ago First seen · 262 lines · 0 tokens per session scan A d0bf5a8eb240
release is a command published in the GitHub repository sergiobayona/vector_mcp (13 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,543 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
Create a new Remarc release using the automated GitHub Actions workflow.
deploy-prod
Create a production deployment PR from main to deploy/prod with auto-versioning.
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.
changelog
Generate a changelog summary for a Linear project and copy to clipboard.
release
Run the standard release flow — bump version, commit, push, open PR, merge, tag, create GitHub release. Use when shipping a new version of gsd-taskmanager.
release
Command "release" from khuynh22/mcp-wireshark, covering how it works, what to tell the user, if no label is added and manual fallback.