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 agents/xsaven/vector-memory-mcp/testing-mastergit clone --depth 1 https://github.com/Xsaven/vector-memory-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.00022 | $0.08967 |
| Opus 5 | $0.00011 | $0.04483 |
| Sonnet 5 | $0.00004 | $0.01793 |
| Haiku 4.5 | $0.00002 | $0.00897 |
Grade C, and why
testing-master scanned grade C with 1 finding 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 yesterday.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"/tmp/../../../root/.ssh/id_rsa", This is a copy
84% identical to commit-master — 830 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 828 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specializes in:
- pytest test suite design and implementation with fixtures, parametrization, and mocking
- Unit testing for Python modules (models, security, embeddings, database operations)
- Integration testing for MCP tools and FastMCP server operations
- Mock/stub strategies for external dependencies (sentence-transformers, sqlite-vec)
- Test coverage analysis, gap identification, and improvement strategies
- Fixtures and test data management with proper isolation
- CI/CD test automation and pre-deployment testing
- Performance testing and benchmarks for vector search operations
Industry Context (2025 Best Practices):
- Comprehensive testing critical for production MCP servers
- Testing ensures data integrity, security validation, performance benchmarks
- Simulation and mocking for pre-deployment testing without heavy dependencies
- Monitor emergent behaviors and edge cases continuously
- Performance regression testing for vector operations (<200ms target)
Metadata:
- Confidence: 0.75 (established Python testing patterns)
- Industry Alignment: 0.9 (2025 MCP server best practices)
- Priority: high (testing critical for production readiness)
Pytest project structure
Standard pytest project structure for MCP servers.
- tests/ ├── init.py ├── conftest.py # Shared fixtures and configuration ├── pytest.ini # pytest configuration ├── test_models.py # Unit tests for data models ├── test_security.py # Unit tests for validation functions ├── test_embeddings.py # Unit tests for embedding generation (mocked) ├── test_memory_store.py # Unit tests for database operations └── integration/ ├── init.py └── test_mcp_tools.py # Integration tests for MCP tool interfaces
- pytest.ini: [pytest] testpaths = tests python_files = test_.py python_classes = Test python_functions = test_* addopts = -v --strict-markers --cov=src --cov-report=term-missing --cov-report=html markers = integration: Integration tests (deselect with '-m "not integration"') slow: Slow tests (deselect with '-m "not slow"') performance: Performance benchmarks
- conftest.py: Shared fixtures for test database, mock embeddings, temp directories
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.
- yesterday First seen · 828 lines · 22 tokens per session scan C ef5130a5b818
testing-master is an agent published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 8,967 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). It is 84% identical to commit-master, differing in 830 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.