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/mesa-tecnica)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/mesa-tecnica"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/mesa-tecnica/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/mesa-tecnica"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/mesa-tecnica.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.00015 | $0.02177 |
| Opus 5 | $0.00008 | $0.01089 |
| Sonnet 5 | $0.00003 | $0.00435 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
mesa-tecnica 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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:mesa-tecnica
Objetivo
Convocar una mesa de expertos técnicos senior — todos con +15 años de experiencia en su área — para discutir decisiones de implementación, patrones de código, elección de stack, performance, y problemas técnicos complejos. Cada experto aporta desde la trinchera: código real, incidentes vividos, y lecciones aprendidas.
A diferencia de /dc:debate (tensión adversarial cross-funcional) y /dc:mesa-redonda (exploración producto-negocio), la mesa técnica es 100% ingeniería: cómo se construye, cómo escala, cómo se mantiene.
Uso
/dc:mesa-tecnica "<tema>"
/dc:mesa-tecnica --roles "Backend,Frontend,Arquitecto" "<tema>"
/dc:mesa-tecnica --preset infra "<tema>"
Roles Disponibles
Core (participan por default)
| Rol | Perfil | Dominio | Aporta |
|---|---|---|---|
| Tech Lead | +15 años liderando equipos técnicos | Decisiones cross-cutting, trade-offs de equipo, priorización técnica | Visión holística, impacto en velocity del equipo, deuda técnica vs entrega, estándares de código |
| Arquitecto | +15 años diseñando sistemas distribuidos | System design, patrones de integración, evolución de arquitectura | Diagramas C4, ADRs, patterns (CQRS, Event Sourcing, Saga), anti-patterns, boundaries |
| Sr. Backend | +15 años en sistemas de alta concurrencia | APIs, bases de datos, colas, caching, concurrencia | Patrones de resiliencia (circuit breaker, retry, bulkhead), optimización de queries, connection pooling, race conditions |
| Sr. Frontend | +15 años en aplicaciones web/mobile complejas | UI frameworks, state management, rendering, bundle optimization | Performance (Core Web Vitals, LCP < 2.5s), SSR vs CSR vs ISR, accesibilidad, design systems, micro-frontends |
| Sr. DevOps/SRE | +15 años en infraestructura y operaciones | CI/CD, containers, observabilidad, incident response | IaC (Terraform/Pulumi), SLOs/SLIs, runbooks, cost optimization, zero-downtime deploys |
Especialistas (invocables con --roles)
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.
- 7d ago First seen · 144 lines · 15 tokens per session scan A 7ab89d39a418
mesa-tecnica is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 2,177 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
add-phase
Add phase to end of current milestone in roadmap.
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
reapply-patches
Reapply local modifications after a PBR update.
add-todo
Capture idea or task as todo from current conversation context.