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/rubocopgit clone --depth 1 https://github.com/sergiobayona/vector_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/sergiobayona/vector_mcp/rubocop)<a href="https://agentmods.dev/commands/sergiobayona/vector_mcp/rubocop"><img src="https://agentmods.dev/badge/commands/sergiobayona/vector_mcp/rubocop.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 | $0.00000 | $0.01362 |
| Opus 5 | $0.00000 | $0.00681 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
rubocop 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 5d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RuboCop Fix All Offenses
Comprehensive workflow for running RuboCop and systematically fixing all style and linting offenses in the VectorMCP Ruby gem.
Overview
This command runs RuboCop to identify all linting and style issues, then systematically fixes them using both automatic fixes and manual corrections where needed.
Steps
1. Pre-check: Git Status
Ensure we're starting from a clean state:
!git status --porcelain
If there are uncommitted changes, commit or stash them first to isolate RuboCop fixes.
2. Initial RuboCop Analysis
Run RuboCop to see current state of offenses:
# Get overview of all offenses
!bundle exec rubocop --format progress
# Get detailed offense breakdown by cop
!bundle exec rubocop --format offenses
Analyze the output:
- Note total offense count
- Identify most common offense types
- Look for auto-correctable offenses
3. Auto-correct Safe Offenses
Fix all safe auto-correctable offenses first:
# Auto-correct safe offenses only
!bundle exec rubocop --auto-correct
# Check remaining offenses after safe corrections
!bundle exec rubocop --format progress
4. Auto-correct Unsafe Offenses (with caution)
Fix unsafe auto-correctable offenses (review changes carefully):
# Auto-correct unsafe offenses (be careful!)
!bundle exec rubocop --auto-correct-all
# Immediately check what changed
!git diff
⚠️ IMPORTANT: Review all changes from unsafe auto-corrections before proceeding.
5. Run Tests After Auto-corrections
Ensure auto-corrections didn't break anything:
!bundle exec rspec
If tests fail, investigate and fix issues before continuing.
6. Manual Fix Remaining Offenses
Address remaining offenses that require manual intervention:
# Show remaining offenses with file locations
!bundle exec rubocop --format simple
# For specific files with many offenses, focus on one file at a time
!bundle exec rubocop lib/vector_mcp/specific_file.rb --format simple
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.
- 5d ago First seen · 205 lines · 0 tokens per session scan A 5178fe40aa53
rubocop is a command published in the GitHub repository sergiobayona/vector_mcp (13 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,362 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
localnest:dashboard
Show a live terminal dashboard with memory stats, KG overview, and server status.
deploy
Generate the exact deploy + test sequence for the current change.
issue-iterate
You are tasked with iterating and evolving GitHub issue specifications based on user reactions and feedback through interactive comment-based refinement.
10-optimization-finalization
Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.