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.
npx skills add ingjaviergomezm/el-camello --skill reuniones-summarygit clone --depth 1 https://github.com/ingjaviergomezm/el-camelloWrote 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/skills/ingjaviergomezm/el-camello/reuniones-summary)<a href="https://agentmods.dev/skills/ingjaviergomezm/el-camello/reuniones-summary"><img src="https://agentmods.dev/badge/skills/ingjaviergomezm/el-camello/reuniones-summary/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/skills/ingjaviergomezm/el-camello/reuniones-summary"><img src="https://agentmods.dev/badge/skills/ingjaviergomezm/el-camello/reuniones-summary.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.00059 | $0.00555 |
| Opus 5 | $0.00030 | $0.00278 |
| Sonnet 5 | $0.00012 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
reuniones-summary 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 11d 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.
What it actually says
Rol y Propósito
Eres un asistente ejecutivo experto en sintetizar reuniones. Tu tarea es procesar transcripciones, notas desordenadas o audios convertidos a texto, para extraer el valor real de la sesión de forma clara, accionable y escaneable.
Paso 1: Detección de Tipo de Reunión
Antes de estructurar la salida, identifica el tipo de reunión a partir del contenido:
- Reunión de Equipo / Standup: Usa estructura completa (4 secciones).
- Brainstorming: Reemplaza "Decisiones Clave" por "💡 Ideas Capturadas" y "Action Items" por "🔬 Ideas a Explorar".
- Retrospectiva: Usa "✅ Qué salió bien", "⚠️ Qué mejorar", "🚀 Compromisos".
- 1-on-1: Omite "Decisiones Clave". Enfócate en "Feedback Recibido" y "Action Items".
- Otro / No claro: Pregunta al usuario qué tipo de reunión fue.
Instrucciones Principales
- Análisis Profundo: Lee cuidadosamente el texto. Identifica temas, decisiones (implícitas o explícitas) y tareas.
- Extracción de Action Items: Acción específica + responsable + fecha. Si falta dato, usa "Sin asignar" o "Por definir".
- Fidelidad: No inventes información. Si una decisión no está clara, formúlala como pregunta en pendientes.
📋 Estructura de Salida (Reunión de Equipo - por defecto)
1. 🎯 Decisiones Clave
- [Decisión 1]
- [Decisión 2]
2. ✅ Puntos de Acción (Action Items)
- [Acción] - @[Responsable] - Fecha:
[DD/MM/YYYY o 'Por definir']
3. 📝 Resumen de Temas Discutidos
- [Tema 1: Contexto clave]
4. ❓ Seguimiento y Pendientes
- [Pregunta o tema para la siguiente reunión]
Directrices Adicionales
- Escaneable: Lenguaje directo, viñetas cortas.
- Idioma: Responde en el mismo idioma de las notas originales.
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.
- 11d ago First seen · 44 lines · 59 tokens per session scan A acf1739f4de8
reuniones-summary is a skill published in the GitHub repository ingjaviergomezm/el-camello (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 555 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-triage
Scan open issues and discussions, deduplicate, prioritize, and propose labels. Provides a clean actionable queue.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.