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.
git clone --depth 1 https://github.com/Mazalucas/El-DT-Lightweight-ArmyWrote 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/mazalucas/el-dt-lightweight-army/prepr)<a href="https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/prepr"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/prepr/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/commands/mazalucas/el-dt-lightweight-army/prepr"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/prepr.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.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
prepr 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 8d 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.
What it actually says
Preparar PR
Prepara los cambios como Pull Request listo para review.
Checklist pre-PR
- Tests: ¿Pasan todos los tests?
- Lint: ¿El código cumple con el linter?
- Resumen de cambios: ¿Qué se modificó y por qué?
- Documentación (
docs/): Si el cambio afecta comportamiento, contratos, arquitectura, ops o guías de repo, ¿está actualizado el doc en la capa correcta (metadata YAML,related,id-registry/catalog.yamlsi aplica)? Si no aplica: N/A + una línea de justificación.
Formato de descripción de PR
## Resumen
[Breve descripción del cambio]
## Cambios
- [ ] Cambio 1
- [ ] Cambio 2
## Cómo probar
[Pasos para verificar]
## Documentación
Incluí en el PR si tocaste `docs/` o si el cambio requería doc: enlace a archivos clave o **N/A**.
## Puntos ciegos
¿Qué podría fallar en review? ¿Qué no está documentado?
Validaciones antes de merge
Sugiere validaciones que el revisor debería hacer:
- Tests relevantes
- Impacto en otras partes del sistema
- Documentación actualizada
Puntos ciegos
Incluye sección: "¿Qué podría fallar en review? ¿Qué no está documentado?"
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.
- 8d ago First seen · 50 lines · 0 tokens per session scan A 2bc1e2dd3bf2
prepr is a command published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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-09-03.
Other commands, from other repositories
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Fetches the comment and diff via gh CLI, classifies it, applies the fix directly to the file if valid, posts a reply on the thread, and resolves it. Run from inside the repo.
ia-review
Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees.
ia-document-release
Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.
prune-sync-log
Prune stale entries from the whetstone sync decision log.
ia-changelog
Create engaging changelogs for recent merges to main branch.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.