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 cumplimientogit 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/cumplimiento)<a href="https://agentmods.dev/skills/betobetico/claude-para-abogados/cumplimiento"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/cumplimiento/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/cumplimiento"><img src="https://agentmods.dev/badge/skills/betobetico/claude-para-abogados/cumplimiento.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.00023 | $0.01130 |
| Opus 5.5 | $0.00009 | $0.00452 |
| Sonnet 5.5 | $0.00005 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
cumplimiento-societario 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propósito
Esta skill genera y mantiene el calendario de obligaciones societarias legales para una entidad mercantil española (SL o SA). Verifica el estado de cumplimiento de cada obligación y alerta sobre plazos próximos o vencidos.
Instrucciones
Paso 1 — Identificar la entidad
- Determinar el tipo de sociedad: SL (Sociedad Limitada) o SA (Sociedad Anónima).
- Recopilar datos relevantes: fecha de cierre del ejercicio, fecha de constitución, órgano de administración, consejeros y sus fechas de nombramiento.
- Cargar configuración específica desde
~/.claude/plugins/config/claude-para-abogados/societario/CLAUDE.md.
Paso 2 — Generar calendario de obligaciones
Obligaciones comunes a SL y SA:
- Formulación de cuentas anuales: 3 meses desde el cierre del ejercicio (art. 253 LSC).
- Aprobación de cuentas anuales: 6 meses desde el cierre (art. 164 LSC) — 30 de junio para ejercicios naturales.
- Depósito de cuentas en el RM: 1 mes desde la aprobación (art. 279 LSC).
- Legalización de libros: 4 meses desde el cierre del ejercicio (art. 18 C.Com).
- Impuesto sobre Sociedades: 25 días naturales tras 6 meses del cierre (25 de julio).
- Renovación de cargos: según duración estatutaria (máx. 6 años SL art. 221, máx. 6 años SA art. 222).
- Libro registro de socios/accionistas: actualización tras cada transmisión.
Obligaciones específicas de SA:
- Informe de gestión: obligatorio (art. 262 LSC).
- Verificación de cuentas por auditor: si procede (art. 263 LSC).
- Junta general ordinaria: obligatoria dentro de los 6 primeros meses.
Paso 3 — Verificar estado
Para cada obligación:
- Cumplida: documentación disponible que acredita el cumplimiento.
- En plazo: el plazo no ha vencido.
- Próxima: vence en los próximos 30 días.
- Vencida: el plazo ha expirado sin acreditar cumplimiento.
Paso 4 — Generar informe
Formato de salida
## Calendario de cumplimiento societario
**Sociedad:** [denominación]
**Tipo:** [SL/SA]
**Ejercicio:** [año]
**Fecha del informe:** [fecha]
### Estado general
- Obligaciones cumplidas: [n]/[total]
- Próximas (≤30 días): [n]
- Vencidas sin cumplir: [n]
### Calendario de obligaciones
| Obligación | Plazo legal | Fecha límite | Estado | Base legal | Notas |
|------------|-------------|--------------|--------|------------|-------|
| Formulación cuentas | 3 meses cierre | [fecha] | [estado] | Art. 253 LSC | [nota] |
| Aprobación cuentas | 6 meses cierre | [fecha] | [estado] | Art. 164 LSC | [nota] |
| Depósito cuentas RM | 1 mes aprobación | [fecha] | [estado] | Art. 279 LSC | [nota] |
### Renovación de cargos
| Cargo | Titular | Fecha nombramiento | Duración | Vencimiento | Estado |
|-------|---------|--------------------|-----------| ------------|--------|
| [cargo] | [nombre] | [fecha] | [años] | [fecha] | [estado] |
### Alertas
[Lista de obligaciones vencidas o próximas con acción recomendada]
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 · 101 lines · 23 tokens per session scan A aed6c6fbda6e
cumplimiento-societario is a skill published in the GitHub repository betobetico/claude-para-abogados (43 stars, last pushed 16d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,130 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.