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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/commands/gonzalezpazmonica/pm-workspace/court-calendar)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/court-calendar"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/court-calendar/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/commands/gonzalezpazmonica/pm-workspace/court-calendar"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/court-calendar.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.00047 | $0.00591 |
| Opus 5.5 | $0.00019 | $0.00236 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
court-calendar 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- court-calendar — 100% identical, 0 lines differ
What it actually says
Calendario Judicial
Organiza y sincroniza comparecencias y vistas judiciales con detección de conflictos.
Uso
court-calendar import <caso> <juzgado> <fecha> <hora> [tipo]
court-calendar sync <archivo-ics>
court-calendar list [próximos-días]
court-calendar conflict
court-calendar export <formato>
Subcomandos
import
Añade fecha judicial manualmente.
caso: referencia del casojuzgado: nombre/número del juzgadofecha: fecha (YYYY-MM-DD)hora: hora (HH:MM)tipo: vista|juicio|comparecencia (default: comparecencia)
Almacena en: projects/{proyecto}/legal/court-calendar.json
sync
Lee e importa fechas desde archivo ICS.
archivo-ics: ruta del archivo de calendario- Parsea eventos y crea entradas
- Vincula a plazos legales existentes
list
Muestra próximas comparecencias judiciales.
próximos-días: rango de visualización (default: 30)- Muestra: caso, juzgado, fecha, hora, tipo, abogado
conflict
Detecta conflictos de agenda.
- Identifica: mismo abogado, horarios superpuestos
- Considera tiempo de desplazamiento (1h por defecto)
- Sugerencias de reprogramación
- Filtra por abogado/período
export
Exporta calendario a formato ICS.
- Compatible con Outlook, Google Calendar, Apple Calendar
- Incluye detalles: caso, juzgado, contactos
Almacenamiento
{
"court_dates": [
{
"id": "cd-001",
"case": "C-2024-001",
"court": "Juzgado 5 Mercantil",
"date": "2026-03-25",
"time": "10:30",
"type": "vista",
"assigned_to": "Abogado 1",
"address": "Paseo de Recoletos 25",
"deadline_id": "plazo-001"
}
]
}
Vinculación
- Cada entrada de juzgado vincula a plazo legal
- Alertas sincronizadas con deadline
- Historial de cambios registrado
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.
- 1mo ago First seen · 92 lines · 47 tokens per session scan A 2bd12f05917f
court-calendar is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (50 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 591 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
service-assessment
Prepare for GDS Service Standard assessment - analyze evidence against 14 points, identify gaps, generate readiness report.
dos
Generate Digital Outcomes and Specialists (DOS7) procurement documentation for the Contract Award Service.
risk
Create comprehensive risk register following HM Treasury Orange Book principles.
change-order
Draft change order documentation with scope changes, cost impacts, schedule adjustments, and approval routing.
score
Score vendor proposals against evaluation criteria with persistent structured storage.
sow
Generate Statement of Work (SOW) / RFP document for vendor procurement.