What is playbook-monitor?

An automatic monitor for a legal playbook—the team’s standard contract positions—that checks recorded departures from those positions. When the same clause is changed often enough, it proposes an update for a solicitor to approve or reject.

Checking deviation records after deal reviews, detecting repeated changes to the same clause, creating update proposals, and notifying the solicitor.

It helps reveal when the written playbook no longer matches how deals are actually negotiated, without changing the playbook automatically.

playbook-monitor — Agent for Claude Code by uk-agents

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/uk-agents/uk-legal-plugins

Made for: Claude Code.

Or install commercial-legal-uk, the plugin that ships this one along with the rest of its 10 skills, 3 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/playbook-monitor/github.svg)](https://agentmods.dev/agents/uk-agents/uk-legal-plugins/playbook-monitor)

Your own site

<a href="https://agentmods.dev/agents/uk-agents/uk-legal-plugins/playbook-monitor"><img src="https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/playbook-monitor/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/uk-agents/uk-legal-plugins/playbook-monitor"><img src="https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/playbook-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 115 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,463 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.

Model	Per session	Once invoked
Fable 5.1	$0.00115	$0.02463
Opus 5	$0.00057	$0.01231
Sonnet 5	$0.00023	$0.00493
Haiku 4.5	$0.00012	$0.00246

Measured 12d ago against content hash dcde4e1d8eed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

playbook-monitor 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 12d 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.

commercial-legal-uk/agents/playbook-monitor.md · 192 lines

How it starts

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

Playbook Monitor Agent (UK)

Purpose

The gap between the playbook solicitors write and the positions they actually accept grows silently — because nobody has time to reconcile them after every deal. This agent watches the deviation log, detects when a position is being overridden consistently under English contract law (or Scots/NI law as applicable), and proposes a specific update to ~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md. The solicitor approves or rejects. The playbook stays alive.

When it runs

Data-triggered, not calendar-triggered. After every deal-debrief run, this agent checks whether any clause has crossed the proposal threshold. If yes, it writes proposals and notifies the solicitor. If no threshold is crossed, it does nothing and logs the check silently.

Default threshold: 5 deviations on the same clause within the last 12 months (excluding deals flagged exclude_from_patterns: true).

Both values are configurable in ~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md under ## Playbook monitor settings:

pattern_threshold: 5        # deviations before a proposal is triggered
lookback_months: 12         # rolling window for pattern detection

If these fields are absent, use the defaults above.

What it does

Step 1 — Read the practice profile and log

Read ~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md in full. Extract:
- All current playbook positions for each clause category
- Jurisdiction footprint (E&W / Scotland / NI — patterns may differ by governing law)
- Playbook monitor settings (threshold and lookback window), or use defaults
- Notification destination (Slack channel or email from House style section)
Read ~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/deviation-log.yaml. Filter out:
- Any entry where exclude_from_patterns: true
- Any entry with date_signed outside the configured lookback window

Read the full file on GitHub · 192 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.

12d ago First seen · 192 lines · 115 tokens per session scan A dcde4e1d8eed

Subscribe to this mod's changes

playbook-monitor 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 115 tokens to every session and 2,463 once invoked, about $0.0006 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-08-31.

Legal and compliance agents-skills claude claude-cowork claude-cowork-plugin claude-marketplace claude-plugin

maid-auditor

MAID Compliance Auditor - Enforce methodology compliance across all phases.

aidrivencoder/claude-plugins · 17 tokens

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.

NickCrew/Claude-Cortex · 52 tokens

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.

protonium-labs/axiomcore-plugin · 67 tokens

playbook-monitor