Borrowing it
Nothing to install: this file belongs to davidbuenov/dbv-specs-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidbuenov/dbv-specs-ops/master/.claude/commands/code-simplify.mdgit clone --depth 1 https://github.com/davidbuenov/dbv-specs-opsWrote 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/davidbuenov/dbv-specs-ops/code-simplify)<a href="https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/code-simplify"><img src="https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/code-simplify/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/davidbuenov/dbv-specs-ops/code-simplify"><img src="https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/code-simplify.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.00023 | $0.01086 |
| Opus 5.5 | $0.00009 | $0.00434 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
code-simplify 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 4d 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.
This is a copy
91% identical to code-simplify — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Ejecuta ahora la fase Simplify (/code-simplify) del ciclo Spec→Plan→Build→Test→Simplify→Ship
definido en dbv-specs-ops/docs/MASTER_PROMPT.md (<workflow>, paso 5). Sigue los tres pases con
severidad de dbv-specs-ops/docs/REVIEW.md (Bugs / Seguridad / Cumplimiento), resuelve todo hallazgo
Crítico, registra lo Importante en dbv-specs-ops/CHANGELOG.md, y después refactoriza para reducir
complejidad sin añadir funcionalidad nueva ("clarity over cleverness"). Si hay Python 3.8+, ejecuta
también python dbv-specs-ops/scripts/dbv-lint.py --changed.
🕸️ Grafo de fases — nodo activo: Simplify
Fase 5: revisión en tres pases (docs/REVIEW.md), dbv-lint.py y refactor de claridad.
Al entrar — la transición por la que llegas fija la condición, cómo ejecutar esta fase y qué evitar:
- desde Test (PROVIDES_INPUT_FOR) — si: Todos los tests y Evals pasan, y ningún requisito con ID de la tarea se queda sin test.
- Cómo: Haz los tres pases de docs/REVIEW.md (Bugs, Seguridad, Cumplimiento con <coding_standards>) y, si hay Python, ejecuta dbv-lint.py --changed. Después refactoriza para dar claridad sin cambiar el comportamiento.
- Evita: No añadas funcionalidad nueva. Si un refactor rompe tests y lo reviertes, regístralo en la Rejection Memory.
- desde Ship (TRIGGERS) — si: El gate de /ship encuentra un hallazgo Crítico sin resolver o la documentación contradice el código.
- Cómo: Vuelve a la revisión por pases solo para resolver lo que bloquea la entrega.
- Evita: No publiques una versión con un Crítico abierto.
Salidas (salto 1) — a dónde puedes ir y con qué condición:
- Simplify → Build (TRIGGERS) — si: La revisión deja un hallazgo Crítico que exige cambiar el comportamiento del código, o un refactor rompe los tests.
- Cómo: Vuelve a Build solo para ese hallazgo y repasa Test antes de regresar a Simplify.
- Evita: No mezcles la corrección con funcionalidad nueva. No ocultes el hallazgo rebajando su severidad.
- Simplify → Ship (CONVERGES_TO) — si: Cero hallazgos Crítico, dbv-lint.py sin errores (si aplica) y tests en verde tras el refactor.
- Cómo: Imprime <memory_update_proposal>. Actualiza README.md de la raíz, sincroniza DESIGN.md derivado si existe, completa walkthrough.md, pregunta el tipo de versión, publica CHANGELOG.md y propone commit + tag.
- Evita: No ejecutes git push (solo sugiérelo). No cierres sin <memory_update_proposal>. No generes start/stop en apps de escritorio, librerías o CLIs.
Horizonte (salto 2) — lo que vendrá después y revisará tu trabajo:
- Build → Test (LEADS_TO) — si: La porción está implementada, compila o se ejecuta sin errores y está anotada en CHANGELOG.md.
- Cómo: Escribe y ejecuta tests deterministas que citen @spec REQ-NN para cada requisito tocado. Con componentes de IA, añade Evals; con un Agent Plugin, valida plugin.json y mcp.json.
- Evita: No marques una tarea como hecha sin un test en verde. Si un enfoque falla y lo reviertes, regístralo en la Rejection Memory antes de probar otro.
- Ship ↩ Simplify (TRIGGERS) — si: El gate de /ship encuentra un hallazgo Crítico sin resolver o la documentación contradice el código.
- Ship → End (LEADS_TO) — si: Versión elegida por el usuario, CHANGELOG.md publicado, commit y tag propuestos.
- Cómo: Guarda el Snapshot de Contexto en task.md y resume al usuario lo entregado.
- Evita: No dejes ficheros temporales ni cambios sin reflejar en task.md.
Rutas relativas a dbv-specs-ops/. Lee la 🚫 Rejection Memory de memory.md antes de proponer un enfoque: lo que ya se descartó no se vuelve a proponer sin explicar qué ha cambiado.
$ARGUMENTS
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.
- 4d ago Changed · +33 lines 9603ff61d587
- 8d ago Changed · +1 lines b21d19114971
- 1mo ago First seen · 11 lines · 23 tokens per session scan A 494af31e5c3b
code-simplify is a command published in the GitHub repository davidbuenov/dbv-specs-ops (29 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 1,086 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to code-simplify, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.