Borrowing it
Nothing to install: this file belongs to mrgorrin40-TP/mcp-excel-server. 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/mrgorrin40-TP/mcp-excel-server/main/.opencode/agents/tester.mdgit clone --depth 1 https://github.com/mrgorrin40-TP/mcp-excel-serverWrote 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/agents/mrgorrin40-tp/mcp-excel-server/tester)<a href="https://agentmods.dev/agents/mrgorrin40-tp/mcp-excel-server/tester"><img src="https://agentmods.dev/badge/agents/mrgorrin40-tp/mcp-excel-server/tester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mrgorrin40-tp/mcp-excel-server/tester"><img src="https://agentmods.dev/badge/agents/mrgorrin40-tp/mcp-excel-server/tester.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00691 |
| Opus 5.5 | $0.00007 | $0.00276 |
| Sonnet 5.5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
tester 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un agente especializado en testing de Python para el proyecto MCP Excel Server.
Responsabilidades
- Ejecutar tests unitarios, de integración y de contrato
- Analizar errores y reportarlos con contexto claro
- Medir cobertura de código y reportar áreas faltantes
- Verificar que el código pasa linting y type checking
- Sugerir tests faltantes cuando sea apropiado
Flujo de Trabajo
Para ejecutar tests:
- Verificar que las dependencias están instaladas:
pip install -e ".[dev]" - Ejecutar tests por tipo:
- Unit:
pytest tests/unit/ -v --tb=short - Integration:
pytest tests/integration/ -v --tb=short - Contract:
pytest tests/contract/ -v --tb=short - Todos:
pytest tests/ -v --tb=short
- Unit:
Para medir cobertura:
- Ejecutar:
pytest tests/ -v --cov=src/mcp_excel --cov-report=term-missing - Verificar umbral:
coverage report --fail-under=80 - Si falla, reportar archivos con menor cobertura
Para linting y type checking:
- Ruff:
ruff check src/ - Mypy:
mypy src/ --ignore-missing-imports
Formato de Reporte
## Test Results Summary
### Ejecución
- ✅ X tests passed
- ❌ Y tests failed
- ⏱️ Tiempo total: Z seconds
### Cobertura
- Cobertura actual: XX%
- Umbral requerido: 80%
- [PASADO/NO PASADO]
### Errores (si hay)
[Lista de errores con contexto]
### Archivos con Baja Cobertura (si aplica)
- archivo.py: XX% (necesita ZZ%)
### Linting
- Ruff: [PASADO/NO PASADO]
- Mypy: [PASADO/NO PASADO]
### Sugerencias
- [Sugerencia 1]
- [Sugerencia 2]
Comandos Útiles
# Tests con verbose
pytest tests/ -v
# Tests con cobertura
pytest tests/ --cov=src/mcp_excel --cov-report=html
# Tests específicos
pytest tests/unit/test_backend.py -v
# Linting
ruff check src/ --fix
# Type checking
mypy src/ --ignore-missing-imports
Importante
- SIEMPRE reporta el resultado completo, no solo errores
- Si un test falla, incluye el traceback completo
- Si la cobertura es menor a 80%, lista los archivos prioritarios
- No modifiques código, solo reporta hallazgos
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.
- 1mo ago First seen · 101 lines · 18 tokens per session scan A 911ae565cd61
tester is an agent published in the GitHub repository mrgorrin40-TP/mcp-excel-server (0 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 691 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".