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/fermonterom/claude-testing-kit/check-testsgit clone --depth 1 https://github.com/fermonterom/claude-testing-kitWhat 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.03776 |
| Opus 5 | $0.00000 | $0.01888 |
| Sonnet 5 | $0.00000 | $0.00755 |
| Haiku 4.5 | $0.00000 | $0.00378 |
Grade A, and why
check-tests scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s --max-time 2 http://localhost:3000 > /dev/null 2>&1 How it starts
The opening of the file, as written. The whole thing — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/check-tests — Verificar cobertura, seguridad y deploy-readiness
Escanea el proyecto, valida build, env vars, seguridad, tests, y da un score 0-100 con semaforo.
Paso 1: Detectar estructura del proyecto
Antes de buscar archivos, detectar donde esta la carpeta app/:
# Detectar ruta base
if [ -d "src/app" ]; then
APP_DIR="src/app"
elif [ -d "app" ]; then
APP_DIR="app"
else
echo "ERROR: No se encontro carpeta app/ ni src/app/"
exit 1
fi
Usar $APP_DIR en todos los comandos siguientes.
Paso 2: Validar build (30 puntos)
Ejecutar npm run build (o el PM del proyecto). Esto captura errores de TypeScript, imports rotos y problemas de sintaxis — las razones mas comunes de deploys fallidos.
- Build pasa → 30/30
- Build falla → 0/30 (blocker)
Si falla, traducir los errores a lenguaje claro. En vez de mostrar la salida cruda del compilador, decir cosas como: "Error de TypeScript en src/app/page.tsx linea 42 — estas tratando un numero como string."
Si el script build no existe en package.json, omitir este paso y asignar 30/30 con nota: "No hay script de build configurado".
Paso 3: Escanear variables de entorno (20 puntos)
Las env vars faltantes son la causa #1 de deploys rotos — el proyecto funciona local pero se rompe en Vercel.
3.1 Buscar todas las referencias
# Buscar process.env.* e import.meta.env.* en archivos TS/TSX/JS (excluyendo node_modules, .next, dist)
grep -roEh 'process\.env\.[A-Za-z_][A-Za-z0-9_]*' --include='*.ts' --include='*.tsx' --include='*.js' --include='*.mjs' --exclude-dir=node_modules --exclude-dir=.next --exclude-dir=dist . 2>/dev/null | sort -u
grep -roEh 'import\.meta\.env\.[A-Za-z_][A-Za-z0-9_]*' --include='*.ts' --include='*.tsx' --exclude-dir=node_modules --exclude-dir=.next . 2>/dev/null | sort -u
Excluir de la busqueda:
node_modules/,.next/,dist/,build/- Archivos de config (vitest.config.ts, playwright.config.ts, next.config.*)
- Variables estandar de Node/Next que no necesitan
.env:NODE_ENV,CI,VERCEL,NEXT_RUNTIME,ANALYZE
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 · 382 lines · 0 tokens per session scan A 4665e35eabb4
check-tests is a command published in the GitHub repository fermonterom/claude-testing-kit (10 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,776 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.