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/polmarza/project-template/doctorgit clone --depth 1 https://github.com/polmarza/project-templateWrote 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/commands/polmarza/project-template/doctor)<a href="https://agentmods.dev/commands/polmarza/project-template/doctor"><img src="https://agentmods.dev/badge/commands/polmarza/project-template/doctor.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.00000 | $0.00830 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
doctor 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revisa el estado del proyecto y del entorno, y da un parte de qué está bien, qué falta y cómo arreglarlo. Solo diagnostica: no arregla nada por su cuenta. Al terminar, propón las correcciones y deja que el usuario decida cuáles aplicar.
Ejecútalo cuando alguien entra al proyecto por primera vez, cuando algo falla sin motivo aparente o antes de una sesión larga, para no descubrir a mitad que faltaba media configuración.
Qué comprobar
1. Documentación
- ¿Existen todos los archivos que
CLAUDE.mdmarca como obligatorios para este proyecto? (La obligatoriedad depende del tamaño: mira la tabla "Qué documentación necesita cada proyecto".) - ¿Alguno está vacío — solo comentarios
<!-- -->, sin contenido real? - ¿Sigue existiendo
.template/? Entonces la inicialización quedó a medias.
2. Fichas de feature
Ejecuta la verificación de cobertura y reporta su salida tal cual:
node scripts/verificar-cobertura.mjs
Comprueba las tablas contra docs/prd.md: filas sin validación declarada, excepciones que no
explican nada, identificadores inexistentes y tests prometidos que no existen en fichas
Verificada. Sus FALLO son FALLO aquí; sus ATENCIÓN son ATENCIÓN.
Añade a mano lo que el script no mira, porque requiere criterio:
- Fichas en En construcción: son trabajo a medias. Di cuáles y desde cuándo.
- Tests declarados que existen pero están vacíos o sin aserciones reales. El script solo comprueba que el archivo esté ahí; si te cruzas con uno hueco, es un FALLO aunque la verificación pase.
3. Entorno
- Versión de Node y de pnpm frente a lo que declare
CLAUDE.md. Si no coinciden, dilo: la mayoría de fallos raros de instalación son esto. - ¿Están las dependencias instaladas (
node_modules/)? ¿El lockfile está al día respecto apackage.json? - Variables: compara los nombres de
.env.examplecon los que hay definidos en el entorno o en.env.local. Reporta solo los nombres que faltan. Nunca imprimas un valor, ni completo ni parcial, ni siquiera para confirmar que es correcto.
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 · 73 lines · 0 tokens per session scan A 49ee1a29754b
doctor is a command published in the GitHub repository polmarza/project-template (79 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 830 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.