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 betobetico/claude-para-abogados --skill gapsgit clone --depth 1 https://github.com/betobetico/claude-para-abogadosWrote 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/betobetico/claude-para-abogados/gaps)<a href="https://agentmods.dev/skills/betobetico/claude-para-abogados/gaps"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/gaps/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/betobetico/claude-para-abogados/gaps"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/gaps.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.00079 | $0.01154 |
| Opus 5.5 | $0.00032 | $0.00462 |
| Sonnet 5.5 | $0.00016 | $0.00231 |
| Haiku 4.5 | $0.00008 | $0.00115 |
Grade A, and why
gaps 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 15d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gaps
- Cargar
~/.claude/plugins/config/claude-para-abogados/regulatorio/CLAUDE.md→ registro de gaps, políticas, sectores. - Leer el registro de gaps del directorio de outputs.
- Filtrar según parámetros (sector, prioridad, estado).
- Generar tabla de estado actualizada.
/regulatorio:gaps --prioridad alta
Propósito
Un gap regulatorio identificado pero no cerrado es un riesgo latente. Este skill mantiene la visibilidad sobre todos los gaps abiertos: cuáles se han identificado, cuáles están en análisis, cuáles tienen propuesta de solución y cuáles se han cerrado. Es el tablero de control del compliance regulatorio.
Ciclo de vida de un gap
IDENTIFICADO → EN ANÁLISIS → PROPUESTA ENVIADA → IMPLEMENTADO → CERRADO
| Estado | Significado | Responsable |
|---|---|---|
| Identificado | Gap detectado (por /regulatorio:diff, /regulatorio:alertas o manualmente) |
Compliance |
| En análisis | Se está evaluando el impacto y la solución | Compliance + Área afectada |
| Propuesta enviada | Se ha redactado la actualización y enviado para aprobación | Policy owner |
| Implementado | La política/procedimiento se ha actualizado | Compliance |
| Cerrado | Verificado que la implementación es correcta y completa | Compliance |
Priorización
| Prioridad | Criterio | Plazo objetivo |
|---|---|---|
| Alta | Incumplimiento activo o riesgo de sanción; norma ya en vigor sin período transitorio | Inmediato (días) |
| Media | Desalineación significativa con período transitorio o riesgo moderado | Semanas |
| Baja | Mejora recomendable; gap menor sin riesgo directo de sanción | Meses |
Formato del registro de gaps
Cada gap se registra con:
| Campo | Contenido |
|---|---|
| ID | Identificador único (ej., GAP-2026-001) |
| Fecha de identificación | [fecha] |
| Origen | [diff / alerta / auditoría / manual] |
| Cambio regulatorio | [referencia a la norma/guía] |
| Política afectada | [nombre de la política interna] |
| Descripción del gap | [qué falta o qué está desalineado] |
| Prioridad | [Alta / Media / Baja] |
| Estado | [Identificado / En análisis / Propuesta enviada / Implementado / Cerrado] |
| Responsable | [persona o equipo] |
| Fecha objetivo | [cuándo debe estar cerrado] |
| Notas | [contexto adicional] |
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.
- 15d ago First seen · 138 lines · 79 tokens per session scan A cc31e3eb5a0a
gaps is a skill published in the GitHub repository betobetico/claude-para-abogados (43 stars, last pushed 16d ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,154 once invoked, about $0.0003 per session on Opus 5.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-10-01.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
subpoena-triage
Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a subpoena", "served with a subpoena", or shares a subpoena, CID, or third-party document request…
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.