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/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/code-improve)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/code-improve"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/code-improve.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.1 | $0.00021 | $0.00683 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
code-improve 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code-improve
Lanza un bucle autónomo de mejora de código inspirado en autoresearch. Detecta oportunidades, aplica mejoras medibles, y genera PRs pendientes de revisión humana.
1. Cargar configuración
- Leer
@docs/rules/domain/autonomous-safety.md— reglas de seguridad (OBLIGATORIO) - Leer
@docs/rules/domain/pm-config.md+pm-config.local.md - Leer
.opencode/skills/code-improvement-loop/SKILL.md
2. Uso
/code-improve [--project {nombre}] [--scope {path}] [--tipo {coverage|complexity|lint|deps|todos|all}] [--max-tasks {n}] [--dry-run]
--project: Proyecto específico (default: proyecto activo)--scope: Limitar a una ruta específica (default: todo el proyecto)--tipo: Tipo de mejora (default:all)--max-tasks: Máximo de mejoras a intentar--dry-run: Solo detectar oportunidades sin aplicar
3. Gate de arranque
✅ AUTONOMOUS_REVIEWER configurado → si no: ❌ ABORT
✅ Tests del proyecto pasan → si no: ❌ "Baseline roto"
4. Detección y confirmación
Mostrar oportunidades detectadas:
🔄 Code Improvement Loop — {proyecto}
📊 Métricas baseline:
Cobertura: 67.3%
Complejidad máx: 18 (src/api/handler.ts)
Warnings linter: 42
TODOs sin ticket: 8
Deps desactualizadas: 3
📋 Oportunidades detectadas: {n}
1. [coverage] src/auth/ — cobertura 42% → objetivo 80%
2. [complexity] src/api/handler.ts — complejidad 18 → objetivo ≤10
3. [lint] src/ — 42 warnings corregibles
...
👤 Reviewer: {AUTONOMOUS_REVIEWER}
⏱️ Time-box por tarea: {AGENT_TASK_TIMEOUT_MINUTES} min
¿Confirmar arranque? (s/n)
5. Output
🔄 Code Improvement — Completado
✅ PRs creados: {n}
⚠️ Descartados (métricas no mejoraron): {n}
❌ Crashes: {n}
📊 Mejoras propuestas:
Cobertura: 67.3% → 78.1% (+10.8%) [3 PRs]
Complejidad máx: 18 → 12 (-6) [1 PR]
Warnings: 42 → 15 (-27) [2 PRs]
📄 Resultados: output/improvement-results-{fecha}.tsv
📝 Audit log: output/agent-runs/improvement-{fecha}-audit.log
⚡ /compact
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 · 81 lines · 21 tokens per session scan A 2e98cbc8a170
code-improve is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 683 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
pr
Automated PR code quality review with language-aware analysis and project-specific profiles.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
gsd-quality
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
p5-impl-refactor
Improves code quality without changing behavior. All tests must continue to pass.