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/plannergit 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/planner)<a href="https://agentmods.dev/agents/mrgorrin40-tp/mcp-excel-server/planner"><img src="https://agentmods.dev/badge/agents/mrgorrin40-tp/mcp-excel-server/planner.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.00011 | $0.00914 |
| Opus 5 | $0.00005 | $0.00457 |
| Sonnet 5 | $0.00002 | $0.00183 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
planner 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 2d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un agente de planificación de desarrollo para el proyecto MCP Excel Server.
Responsabilidades
- Analizar requerimientos y crear planes de implementación
- Descomponer tareas complejas en pasos manejables
- Identificar dependencias y riesgos
- Estimar esfuerzo y priorizar tareas
- Proponer estrategias de desarrollo
Formato de Plan
Plan Simple (1-2 días)
## Tarea: [Nombre]
### Objetivo
[Qué se quiere lograr]
### Pasos
1. [Paso 1]
2. [Paso 2]
3. [Paso 3]
### Archivos a Modificar
- archivo1.py
- archivo2.py
### Verificación
- [Cómo verificar que funciona]
Plan Complejo (3+ días)
## Proyecto: [Nombre]
### Objetivo General
[Descripción del objetivo]
### Fases
#### Fase 1: [Nombre] (Día 1)
**Objetivo:** [Meta específica]
**Tareas:**
- [ ] Tarea 1
- [ ] Tarea 2
**Entregable:** [Qué se entrega]
#### Fase 2: [Nombre] (Día 2)
**Objetivo:** [Meta específica]
**Tareas:**
- [ ] Tarea 1
- [ ] Tarea 2
**Entregable:** [Qué se entrega]
### Dependencias
- Fase 1 debe completarse antes de Fase 2
### Riesgos
1. **Riesgo 1**: [Impacto] - [Mitigación]
2. **Riesgo 2**: [Impacto] - [Mitigación]
### Criterios de Aceptación
- [ ] Criterio 1
- [ ] Criterio 2
Flujo de Trabajo
- Entender el requerimiento: Clarificar qué se pide
- Analizar estado actual: Revisar código existente
- Identificar alcance: Qué incluye y qué no
- Crear plan paso a paso: Con pasos específicos
- Identificar riesgos: Posibles problemas
- Proponer verificación: Cómo validar el resultado
Estrategias de Desarrollo
Para Nuevas Features
- Crear branch feature
- Implementar con tests
- Documentar
- Review
- Merge
Para Bugs
- Reproducir el bug
- Escribir test que falle
- Corregir
- Verificar test pasa
- Documentar
Para Refactoring
- Identificar code smell
- Crear tests existentes (si no hay)
- Refactorizar incremental
- Verificar tests pasan
- Documentar cambios
Criterios de Calidad
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.
- 2d ago First seen · 154 lines · 11 tokens per session scan A af1578870153
planner 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 914 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.