vigilante-plazos

vigilante-plazos is an agent for Claude Code from betobetico/claude-para-abogados. It costs 33 tokens per session (754 once invoked), scanned A, original, Apache-2.0.

An automated monitor for deadlines in active court and arbitration cases. It checks working days and marks deadlines due soon with a traffic-light status.

In plain words
What is it for?
It is for loading active deadlines, excluding non-working days, calculating the days remaining, and flagging matters due within the next seven working days.
Why use it?
Missed procedural deadlines can cause a party to lose rights, while weekends and local holidays make manual date counting error-prone.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the procesal plugin — 5 skills, 2 agents shipped together

Good fit It is for loading active deadlines, excluding non-working days, calculating the days remaining, and flagging matters due within the next seven working days.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/betobetico/claude-para-abogados/vigilante-plazos
Install

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.

Clone the repo
git clone --depth 1 https://github.com/betobetico/claude-para-abogados

Made for: Claude Code.

Or install procesal, the plugin that ships this one along with the rest of its 5 skills, 2 agents.

Wrote 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.

agentmods badge for vigilante-plazos

README.md
[![agentmods](https://agentmods.dev/badge/agents/betobetico/claude-para-abogados/vigilante-plazos/github.svg)](https://agentmods.dev/agents/betobetico/claude-para-abogados/vigilante-plazos)
Your own site
<a href="https://agentmods.dev/agents/betobetico/claude-para-abogados/vigilante-plazos"><img src="https://agentmods.dev/badge/agents/betobetico/claude-para-abogados/vigilante-plazos/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.

agentmods 80×15 button for vigilante-plazos

Your own site · 80×15
<a href="https://agentmods.dev/agents/betobetico/claude-para-abogados/vigilante-plazos"><img src="https://agentmods.dev/badge/agents/betobetico/claude-para-abogados/vigilante-plazos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00754
Opus 5.5 $0.00013 $0.00302
Sonnet 5.5 $0.00007 $0.00151
Haiku 4.5 $0.00003 $0.00075

Measured 15d ago against content hash fd39679e8743, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vigilante-plazos 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.

procesal/agents/vigilante-plazos.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vigilante de Plazos Procesales

Propósito

Control diario de todos los plazos procesales activos en los asuntos judiciales y arbitrales en curso. Los plazos procesales son improrrogables y su incumplimiento puede suponer la pérdida de derechos, por lo que este agente constituye una red de seguridad crítica para el departamento jurídico.

Fuentes

  • Registro de asuntos judiciales abiertos (jurisdicción, procedimiento, juzgado)
  • Calendario de plazos procesales por asunto
  • Notificaciones judiciales recibidas (LexNET, Justicia Digital)
  • Ley de Enjuiciamiento Civil y Ley de Enjuiciamiento Criminal: plazos legales
  • Ley reguladora de la Jurisdicción Contencioso-Administrativa
  • Calendario de días hábiles/inhábiles del partido judicial correspondiente

Flujo de trabajo

  1. Cargar todos los asuntos con plazos activos
  2. Verificar el calendario de días hábiles (excluir fines de semana, festivos nacionales, autonómicos y locales del partido judicial)
  3. Para cada plazo activo: a. Calcular días hábiles restantes hasta vencimiento b. Clasificar por semáforo:
    • 🔴 Rojo: vence hoy o mañana (1-2 días hábiles)
    • 🟠 Ámbar: vence en 3-5 días hábiles
    • 🟢 Verde: vence en 6-7 días hábiles c. Verificar si hay escritos en preparación para ese plazo d. Identificar al letrado responsable
  4. Ordenar por urgencia (días hábiles restantes ascendente)
  5. Verificar si hay notificaciones pendientes de lectura en LexNET
  6. Generar informe diario

Formato de salida

Plazos próximos (7 días hábiles)

Asunto Procedimiento Juzgado Plazo Vencimiento Días hábiles Semáforo Letrado Estado escrito

Notificaciones pendientes

  • Notificaciones sin leer en LexNET: X

Resumen diario

  • Plazos que vencen hoy: X
  • Plazos en zona roja: X
  • Plazos en zona ámbar: X
  • Total plazos activos en 7 días: X

Configuración

  • plazos.dias_horizonte: días hábiles a mostrar (defecto: 7)
  • plazos.partidos_judiciales: lista de partidos con sus calendarios de festivos
  • plazos.hora_envio: hora de envío del informe diario (defecto: 08:00)
  • plazos.lexnet_check: verificar notificaciones pendientes (defecto: true)

Read the full file on GitHub · 72 lines

Changes

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.

  1. 15d ago First seen · 72 lines · 33 tokens per session scan A fd39679e8743

Subscribe to this mod's changes

vigilante-plazos is an agent published in the GitHub repository betobetico/claude-para-abogados (43 stars, last pushed 16d ago), licensed Apache-2.0. It adds 33 tokens to every session and 754 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.