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 checklist-cierregit 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/checklist-cierre)<a href="https://agentmods.dev/skills/betobetico/claude-para-abogados/checklist-cierre"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/checklist-cierre/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/checklist-cierre"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/checklist-cierre.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.00026 | $0.01076 |
| Opus 5.5 | $0.00010 | $0.00430 |
| Sonnet 5.5 | $0.00005 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
checklist-cierre-ma 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propósito
Esta skill gestiona la checklist de cierre (closing checklist) de una operación de M&A. Rastrea el estado de cada condición precedente, consentimiento de terceros y documento pendiente de entrega. Diseñada para mantener visibilidad sobre el progreso hacia el cierre de la operación.
Instrucciones
Paso 1 — Extraer condiciones del SPA
- Leer el contrato de compraventa (SPA) o el listado de condiciones precedentes proporcionado.
- Identificar todas las condiciones de cierre:
- Condiciones precedentes (CPs): autorizaciones, consentimientos, certificados.
- Documentos de cierre: escrituras, poderes, certificados, cartas.
- Consentimientos de terceros: cambio de control, waiver de socios, autorización regulatoria.
- Acciones previas al cierre: reorganizaciones, distribuciones, cancelaciones.
Paso 2 — Asignar responsable y plazo
Para cada elemento:
- Responsable: quién debe completarlo (comprador, vendedor, target, asesores, notario, registrador).
- Plazo: fecha límite o condición temporal (ej. "antes del cierre", "5 días tras firma").
- Dependencias: si un elemento depende de otro previo.
Paso 3 — Clasificar estado
- Pendiente: no iniciado.
- En curso: trabajo en progreso, con detalle de próximo paso.
- Completado: entregado y conforme.
- Bloqueado: depende de un elemento que no avanza — indicar cuál.
- Renunciado: la parte beneficiaria ha renunciado a la condición (waiver).
Paso 4 — Generar checklist
Formato de salida
## Checklist de cierre — [Nombre de la operación]
**Fecha de firma del SPA:** [fecha]
**Fecha prevista de cierre (longstop):** [fecha]
**Días hasta longstop:** [n]
**Estado general:** [n]/[total] completados
### Resumen de progreso
| Estado | Número | Porcentaje |
|--------|--------|------------|
| Completado | [n] | [%] |
| En curso | [n] | [%] |
| Pendiente | [n] | [%] |
| Bloqueado | [n] | [%] |
### Condiciones precedentes
| # | Condición | Responsable | Plazo | Estado | Notas |
|---|-----------|-------------|-------|--------|-------|
| CP-1 | [descripción] | [parte] | [fecha] | [estado] | [detalle] |
### Consentimientos de terceros
| # | Consentimiento | Tercero | Responsable | Estado | Notas |
|---|----------------|---------|-------------|--------|-------|
| C-1 | [descripción] | [nombre] | [parte] | [estado] | [detalle] |
### Documentos de cierre
| # | Documento | Responsable | Estado | Notas |
|---|-----------|-------------|--------|-------|
| D-1 | [descripción] | [parte] | [estado] | [detalle] |
### Elementos bloqueados
| Elemento | Bloqueado por | Acción requerida | Responsable |
|----------|---------------|------------------|-------------|
| [ref] | [ref] | [acción] | [parte] |
### Próximos pasos
[Lista priorizada de acciones para avanzar hacia el cierre]
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 · 106 lines · 26 tokens per session scan A 05ed06fec3d9
checklist-cierre-ma is a skill published in the GitHub repository betobetico/claude-para-abogados (43 stars, last pushed 16d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,076 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.
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.