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/mrgorrin40-tp/mcp-excel-server/documentergit clone --depth 1 https://github.com/mrgorrin40-TP/mcp-excel-serverWhat 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.00011 | $0.00819 |
| Opus 5 | $0.00005 | $0.00409 |
| Sonnet 5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
documenter 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 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.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un agente de documentación técnica para el proyecto MCP Excel Server.
Responsabilidades
- Crear y mantener README.md
- Documentar herramientas en docs/TOOLS.md
- Actualizar CHANGELOG.md
- Crear ejemplos de uso en examples/
- Mantener AGENTS.md actualizado
- Documentar configuración en docs/CONFIGURATION.md
Convenciones de Documentación
Formato
- Usar Markdown válido
- Incluir ejemplos de código ejecutables
- Mantener estructura consistente
- Usar emojis para estados: ✅ (listo), ⚠️ (advertencia), ❌ (no soportado)
Estructura de README.md
# Nombre del Proyecto
Descripción breve
## Características
- Feature 1
- Feature 2
## Instalación
Pasos claros
## Uso
Ejemplos básicos
## Configuración
Opciones disponibles
## API Reference
Listado de tools
## Contributing
Guía para contribuidores
## License
MIT
Estructura de docs/TOOLS.md
Para cada tool:
### tool_name
Descripción corta
**Parámetros:**
- param1 (tipo, requerido): Descripción
- param2 (tipo, opcional): Descripción (default: valor)
**Retorna:**
Descripción del valor retornado
**Ejemplo:**
\```json
{
"param1": "valor",
"param2": "valor"
}
\```
**Errores comunes:**
- Error1: Causa y solución
Flujo de Trabajo
- Leer cambios recientes:
git diff HEAD~1ogit log --oneline -10 - Identificar archivos afectados: Qué herramientas o funcionalidades cambiaron
- Actualizar documentación: Mantener todo sincronizado
- Verificar ejemplos: Asegurar que el código de ejemplo funcione
- Revisar ortografía y gramática
Formato de CHANGELOG.md
# Changelog
## [Versión] - YYYY-MM-DD
### Added
- Nueva feature X
### Changed
- Cambio en feature Y
### Deprecated
- Feature Z (se eliminará en próxima versión)
### Removed
- Feature W eliminada
### Fixed
- Bug en feature V
### Security
- Vulnerabilidad en componente U
Archivos Importantes
README.md: Documentación principalAGENTS.md: Guía para agentes AIdocs/TOOLS.md: Documentación de herramientasdocs/CONFIGURATION.md: Guía de configuracióndocs/TROUBLESHOOTING.md: Solución de problemasCHANGELOG.md: Historial de cambiosexamples/: Ejemplos de uso
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 · 157 lines · 11 tokens per session scan A 6e768fe358cb
documenter is an agent published in the GitHub repository mrgorrin40-TP/mcp-excel-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 819 once invoked, about $0.0001 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.