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/rspecgit 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.00009 | $0.00144 |
| Opus 5 | $0.00005 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
rspec 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 3d 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
RSpec Test Generator
Generate comprehensive RSpec tests for the specified Ruby class or method: $ARGUMENTS
Requirements:
- Follow RSpec best practices
- Include both positive and negative test cases
- Use proper describe/context/it structure
- Include edge cases and error conditions
- Use appropriate matchers and helpers
- Follow the project's existing test patterns
Current test structure:
!find spec -name "*.rb" | head -5 | xargs ls -la
Project's RSpec configuration:
@spec/spec_helper.rb
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.
- 3d ago First seen · 23 lines · 9 tokens per session scan A ead39e2207b6
rspec is a command published in the GitHub repository sergiobayona/vector_mcp (13 stars, last pushed 16d ago), licensed MIT. It adds 9 tokens to every session and 144 once invoked, about $0.0000 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
format-sync
Mirror a data-format change across the Rust and Node implementations, prove conformance, and add a fixture.
release-gem
Prepare a release of the gem by running checks, ensuring version is bumped, changelog is updated, and creating a PR.
test-rust
Run Rust tests for Solana programs and backend services.
test
Your mission: Achieve a completely clean test suite with zero failures, warnings, or skipped tests.
5-qa
Test Suite Optimization: Review entire test suite (unit/integration/e2e) for coverage, dependencies, and purpose. Standardize fixtures/mocks per framework conventions. Evaluate test criticality, correct errors/workarounds, remove excessive comments. Maintain simplicity, avoid over-engineering.
6-test
Full Test Suite Execution: Run complete test suite (unit, integration, e2e, evaluation, metrics, performance) to validate all fixes and ensure system reliability. Verify all quality gates pass before proceeding.