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 renovacionesgit 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/renovaciones)<a href="https://agentmods.dev/skills/betobetico/claude-para-abogados/renovaciones"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/renovaciones/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/renovaciones"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/renovaciones.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.00022 | $0.00978 |
| Opus 5.5 | $0.00009 | $0.00391 |
| Sonnet 5.5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
renovaciones-mercantil 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 27d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propósito
Esta skill analiza el registro de contratos mercantiles del despacho o empresa para identificar contratos que se acercan a su fecha de vencimiento, renovación automática o plazo de denuncia. Genera una tabla de próximos vencimientos organizada por urgencia (30, 60 y 90 días).
Instrucciones
Paso 1 — Cargar registro de contratos
- Leer el registro de contratos proporcionado por el usuario (CSV, Excel, JSON o listado de documentos).
- Si no se proporciona registro, solicitar al usuario la fuente de datos.
- Extraer de cada contrato:
- Nombre/identificador del contrato.
- Contraparte.
- Fecha de inicio.
- Fecha de vencimiento.
- Tipo de renovación (automática / manual / no renovable).
- Plazo de preaviso para no renovar (días antes del vencimiento).
- Responsable interno.
Paso 2 — Calcular fechas críticas
Para cada contrato:
- Fecha de vencimiento: cuándo expira el contrato.
- Fecha límite de denuncia: vencimiento menos plazo de preaviso.
- Días restantes: desde hoy hasta cada fecha crítica.
- Estado:
- URGENTE: fecha límite de denuncia en los próximos 30 días.
- ATENCIÓN: fecha límite de denuncia entre 31 y 60 días.
- PLANIFICAR: fecha límite de denuncia entre 61 y 90 días.
- VENCIDO: fecha límite de denuncia ya pasada.
Paso 3 — Detectar riesgos
- Contratos con renovación automática cuyo plazo de denuncia ya venció (se renovarán automáticamente).
- Contratos sin fecha de vencimiento registrada.
- Contratos sin responsable asignado.
- Contratos con condiciones de renovación distintas al período original.
Paso 4 — Generar informe
Formato de salida
## Tracker de renovaciones
**Fecha del informe:** [fecha]
**Contratos analizados:** [número]
**Alertas activas:** [número]
### Resumen
- Contratos URGENTE (≤30 días): [número]
- Contratos ATENCIÓN (31-60 días): [número]
- Contratos PLANIFICAR (61-90 días): [número]
- Contratos ya auto-renovados: [número]
### Próximos vencimientos
| Estado | Contrato | Contraparte | Vencimiento | Límite denuncia | Días restantes | Renovación | Responsable |
|--------|----------|-------------|-------------|-----------------|----------------|------------|-------------|
| URGENTE | [nombre] | [parte] | [fecha] | [fecha] | [n] | [tipo] | [nombre] |
| ATENCIÓN | [nombre] | [parte] | [fecha] | [fecha] | [n] | [tipo] | [nombre] |
### Alertas de riesgo
| Contrato | Riesgo | Detalle |
|----------|--------|---------|
| [nombre] | Auto-renovación inminente | Plazo de denuncia vence en [n] días |
| [nombre] | Sin fecha registrada | No se puede calcular vencimiento |
### Acciones recomendadas
1. [Acción concreta para cada contrato urgente]
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.
- 27d ago First seen · 99 lines · 22 tokens per session scan A 7f3acfdbec32
renovaciones-mercantil is a skill published in the GitHub repository betobetico/claude-para-abogados (44 stars, last pushed 27d ago), licensed Apache-2.0. It adds 22 tokens to every session and 978 once invoked, about $0.0001 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.
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.
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.
client-intake
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new…
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by…