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/minar-referencias)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/minar-referencias"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/minar-referencias/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/minar-referencias"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/minar-referencias.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.00010 | $0.01680 |
| Opus 5 | $0.00005 | $0.00840 |
| Sonnet 5 | $0.00002 | $0.00336 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
minar-referencias 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 9d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:minar-referencias
Objetivo
Buscar y evaluar repositorios open-source, snippets y patrones de referencia relevantes para la tarea actual. Reduce el "empezar de cero" proporcionando implementaciones probadas como guía.
Adaptado de DeepCode (HKUDS/DeepCode) — Code Reference Mining Agent: "descubrir repositorios relevantes y construir knowledge graphs para informar la generación de código."
Uso
/dc:minar-referencias "webhook handler con verificación de firma"
/dc:minar-referencias "rate limiter con sliding window"
/dc:minar-referencias --stack node,typescript "auth con JWT refresh"
/dc:minar-referencias --max 5 "graphql subscriptions"
Por Qué Existe
| Sin Minar | Con Minar |
|---|---|
| Implementar desde cero | Partir de patrones probados |
| Descubrir anti-patrones tarde | Conocer pitfalls de antemano |
| Reinventar soluciones comunes | Reutilizar lo que funciona |
| Estimaciones imprecisas | Complejidad real visible |
Comportamiento
Paso 1: Análisis de la Query
Query: "webhook handler con verificación de firma"
├── Conceptos clave: webhook, handler, signature verification
├── Stack detectado: Node.js + TypeScript (de config.yaml)
├── Dominio: API integration, security
└── Complejidad estimada: Media
Paso 2: Búsqueda Multi-Fuente
El comando busca en múltiples fuentes (según disponibilidad):
| Fuente | Método | Qué Busca |
|---|---|---|
| GitHub | API search / web search | Repos con implementaciones similares |
| Proyecto actual | Grep local | Código existente reutilizable |
| CodeRAG | Índice local | Patrones ya indexados |
| Memoria | Engram | Decisiones previas sobre el tema |
Paso 3: Evaluación de Relevancia
Cada resultado se evalúa en 4 dimensiones:
| Dimensión | Peso | Criterio |
|---|---|---|
| Relevancia | 40% | ¿Resuelve el mismo problema? |
| Calidad | 25% | Stars, mantenimiento, tests, docs |
| Compatibilidad | 20% | ¿Mismo stack/framework? |
| Simplicidad | 15% | ¿Es adoptable sin refactor mayor? |
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.
- 9d ago First seen · 215 lines · 10 tokens per session scan A 4fba9b3999ad
minar-referencias is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,680 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.