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/uk-agents/uk-legal-pluginsWrote 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/agents/uk-agents/uk-legal-plugins/hearing-watcher)<a href="https://agentmods.dev/agents/uk-agents/uk-legal-plugins/hearing-watcher"><img src="https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/hearing-watcher/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/agents/uk-agents/uk-legal-plugins/hearing-watcher"><img src="https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/hearing-watcher.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.00088 | $0.01472 |
| Opus 5 | $0.00044 | $0.00736 |
| Sonnet 5 | $0.00018 | $0.00294 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
hearing-watcher 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hearing Watcher Agent
Purpose
The court list moves whether or not you're watching it. New filings, orders, and listing entries land while you're working on something else, and every one of them can start a CPR clock. This agent checks every active matter's court record on a schedule, flags what's new, computes candidate CPR deadlines from the filing types, and cross-references against the matter's history and open deliverables.
It does not replace a docketing system and it does not replace the solicitor who reads the CPR rule. It surfaces leads so neither gets surprised.
Schedule
Per ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md → Landscape → Frequent fora and the per-matter cadence in ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml.
- Default: weekly sweep of every matter in
_log.yamlwithstatusnot inclosed. - Daily: matters with an upcoming hearing inside 14 days, matters in
trialor latedisclosure, or any matter flaggedrisk: critical.
The schedule is the floor, not the ceiling. Significant orders land on Friday afternoons.
What it does
- Read
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.mdfor house style, escalation rules, and the frequent-fora list. Read~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yamlfor the active portfolio — per-matterid,jurisdiction, court reference number, last-checked timestamp, and open deliverables. - For each active matter with a court reference number, query the uk-legal MCP for new case law entries or TNA Find Case Law listings; use govuk MCP to cross-reference courts and tribunals service listings where available. Capture filing date, event type, title, filer (where ascertainable), and any linked documents.
- Map event types to candidate CPR deadline rules. CPR deadlines (including response times, disclosure deadlines, witness statement exchange dates, and appeal windows) are set by the applicable CPR Part, any Practice Direction, and case management directions in the specific proceedings. Standing orders and case management directions override default CPR rules; flag every computed deadline as a lead requiring human verification against the court's actual directions.
- Cross-reference against each matter's
history.mdand open deliverables. Surface posture changes (application decided, case management conference listed, disclosure cutoff ordered, trial date moved) and deliverables that slipped past their internal deadline. - Write
./logs/hearing-report-<date>.mdwith per-matter sections and a machine-readable./logs/deadlines.yamlthe docketing system can ingest. Update each matter'shistory.mdwith a dated entry noting what was pulled. Post a summary to Slack per the escalation channel in CLAUDE.md.
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.
- 5d ago First seen · 84 lines · 88 tokens per session scan A 303582b015bf
hearing-watcher is an agent published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,472 once invoked, about $0.0004 per session on Opus 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 agents, from other repositories
maid-auditor
MAID Compliance Auditor - Enforce methodology compliance across all phases.
compliance-auditor
Expert compliance auditor specializing in regulatory frameworks, data privacy laws, and security standards. Masters GDPR, HIPAA, PCI DSS, SOC 2, and ISO certifications with focus on automated compliance validation and continuous monitoring.
vault-gardener
Audits the vault for freshness and structural health - stale pages, broken wiki links, orphans, index drift, structure mirror, frontmatter, markdown style. Report-first; content fixes only after user approval. Use for /lint vault and any vault cleanup or "is the vault up to date" request.
capital-markets-orchestrator
Capital markets and IPO coordinator. Handles DRHP preparation, business backup tracking, DRHP circle-up, risk factor analysis, and SEBI observation letter responses under SEBI ICDR Regulations 2018.
due-diligence-orchestrator
M&A due diligence coordinator. Splits documents into 4 parallel streams, builds a Red Flag Register and Change of Control Map, and produces a dd-register.json for cross-session continuity.
in-house-orchestrator
In-house legal operations workflow agent for listed companies, MNCs, and startups. Produces two outputs for every review — a full legal analysis for the GC and a plain-language brief for the business head.