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/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/limpiar-slop)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/limpiar-slop"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/limpiar-slop/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/doncheli/don-cheli-sdd/limpiar-slop"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/limpiar-slop.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.00011 | $0.00797 |
| Opus 5 | $0.00005 | $0.00398 |
| Sonnet 5 | $0.00002 | $0.00159 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
limpiar-slop 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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:limpiar-slop
Objetivo
Detectar y eliminar slop — código innecesario, verbose, o sobre-ingenierizado que los modelos de IA generan frecuentemente. Se ejecuta sobre el diff del branch actual vs main.
Adaptado de
deslopde Pro-Workflow (rohitg00/pro-workflow).
Uso
/dc:limpiar-slop # Limpiar branch actual
/dc:limpiar-slop --preview # Solo mostrar, no editar
/dc:limpiar-slop --archivo archivo # Limpiar un solo archivo
Qué es Slop
Código que la IA genera pero que un dev senior eliminaría:
| Patrón de Slop | Ejemplo | Corrección |
|---|---|---|
| Comentarios obvios | // Get the user antes de getUser() |
Eliminar |
| Try/catch defensivo | Try/catch en código interno confiable | Eliminar si no es boundary |
Cast a any |
(data as any).name |
Tipar correctamente |
| Abstracciones prematuras | Factory para un solo uso | Inlinear |
| Nesting profundo | 4+ niveles de if/else | Early returns |
| Re-exports innecesarios | export { thing } from './thing' solo para "limpiar" |
Eliminar |
| Scope creep | Refactors no solicitados | Revertir |
| Docstrings en código no tocado | JSDoc nuevo en funciones existentes | Eliminar |
| Error handling imposible | Catch de errores que no pueden ocurrir | Eliminar |
Comportamiento
- Obtener diff contra main
- Escanear los 9 patrones de slop
- Proponer edits mínimos y focalizados
- Verificar que el comportamiento no cambia (tests)
- Resumir lo limpiado
Output
=== Limpieza de Slop ===
Archivos escaneados: 8
Patrones encontrados: 12
🧹 Comentarios obvios: 5
- src/services/auth.ts:24 — "// Authenticate the user"
- src/services/auth.ts:38 — "// Return the token"
- src/utils/format.ts:12 — "// Format the date"
...
🧹 Try/catch defensivo: 3
- src/services/payment.ts:45 — try/catch en helper interno
- src/db/queries.ts:23 — catch vacío
...
🧹 Abstracciones prematuras: 2
- src/utils/createHandler.ts — Factory usado 1 sola vez
- src/helpers/wrapResponse.ts — Wrapper innecesario
...
🧹 Scope creep: 2
- src/middleware/cors.ts — Refactor no solicitado
...
Tests después de limpieza: ✅ 47/47 pasan
Líneas eliminadas: 34
Comportamiento: sin cambios
Resumen: Eliminados 5 comentarios obvios, 3 try/catch defensivos,
2 abstracciones prematuras, y 2 cambios fuera de scope.
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.
- 6d ago First seen · 89 lines · 11 tokens per session scan A 283d82a90d31
limpiar-slop is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 797 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-09-03.
Other commands, from other repositories
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
review
Run a code review on changed files (or a path you pass).
differential-audit
Audit EARS↔code coherence via a bidirectional differential. With no arguments, opens a scoping conversation that interprets what the user wants audited, maps it to arrows, and captures an explicit EARS selection. With one or more EARS IDs, audits those specs directly using configured defaults. Requires docs/arrows/…
analyze
A command that examines a codebase’s Git history and file structure to find coding patterns and team habits, then records them as reusable documentation.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.
review
You are a helpful coding expert. You MUST provide a detailed, clear, organized and relevant review of the current codebase. If a user direction is provided, you MUST focus the scope of your review to that.