agentmods.dev

playbook-monitor

playbook-monitor is an agent for Claude Code from zhou210712/claude-for-legal-ZH. It costs 113 tokens per session (2,155 once invoked), scanned A, a copy of playbook-monitor, Apache-2.0.

An automated checker for a contract playbook, meaning the team’s agreed positions on contract clauses. It looks at logged departures from those positions and proposes updates when repeated exceptions suggest the playbook no longer matches practice.

In plain words
What is it for?
Use it after deal debriefs to find clauses that were repeatedly negotiated away from the standard position. It helps maintain the team’s contract guidance based on actual signed deals.
Why use it?
Accepted exceptions can accumulate without anyone noticing that the written guidance is outdated. This surfaces recurring changes for an attorney to approve or reject.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Part of the commercial-legal plugin — 9 skills, 3 agents shipped together

not rated 212repo +7 4mo ago A scan 113 tokens copy · 100% Apache-2.0

Good fit Use it after deal debriefs to find clauses that were repeatedly negotiated away from the standard position. It helps maintain the team’s contract guidance based on actual signed deals.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zhou210712/claude-for-legal-zh/playbook-monitor
View source ↗ zhou210712/claude-for-legal-ZH
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/zhou210712/claude-for-legal-ZH

Made for: Claude Code.

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

agentmods badge for playbook-monitor

README.md
[![agentmods](https://agentmods.dev/badge/agents/zhou210712/claude-for-legal-zh/playbook-monitor/github.svg)](https://agentmods.dev/agents/zhou210712/claude-for-legal-zh/playbook-monitor)
Your own site
<a href="https://agentmods.dev/agents/zhou210712/claude-for-legal-zh/playbook-monitor"><img src="https://agentmods.dev/badge/agents/zhou210712/claude-for-legal-zh/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.

agentmods 80×15 button for playbook-monitor

Your own site · 80×15
<a href="https://agentmods.dev/agents/zhou210712/claude-for-legal-zh/playbook-monitor"><img src="https://agentmods.dev/badge/agents/zhou210712/claude-for-legal-zh/playbook-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 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,155 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 100% copy Near-identical to another mod 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.00113 $0.02155
Opus 5 $0.00056 $0.01077
Sonnet 5 $0.00023 $0.00431
Haiku 4.5 $0.00011 $0.00215

Measured 13d ago against content hash c27b772fa010, 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 13d 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.

Origin

This is a copy

100% identical to playbook-monitor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commercial-legal/agents/playbook-monitor.md · 191 lines

How it starts

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

Playbook Monitor Agent

Purpose

The gap between the playbook attorneys 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, and proposes a specific update to ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. The attorney 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 attorney. 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/claude-for-legal/commercial-legal/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 from ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md, use the defaults above.

What it does

Step 1 — Read the practice profile and log

  1. Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md in full. Extract:

    • All current playbook positions for each clause category
    • Playbook monitor settings (threshold and lookback window), or use defaults
    • Notification destination (Slack channel or email from House style section)

  2. Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml. Filter out:

    • Any entry where exclude_from_patterns: true
    • Any entry with date_signed outside the configured lookback window

Step 2 — Detect patterns

For each clause key present in the filtered log, count deviations. Group by:

  • Clause (e.g., limitation_of_liability)
  • Direction of deviation (e.g., "accepted higher cap", "accepted uncapped")
  • Basis (e.g., counterparty_leverage, commercial_priority)

Read the full file on GitHub · 191 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. 13d ago First seen · 191 lines · 113 tokens per session scan A c27b772fa010

Subscribe to this mod's changes

playbook-monitor is an agent published in the GitHub repository zhou210712/claude-for-legal-ZH (212 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 2,155 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to playbook-monitor, differing in 0 lines, and is treated as a copy.

Analytics and metricsLegal and compliance
Related

Other agents, from other repositories

console-compliance-reviewer

Reviews console/platform compliance, certification risk, and release checklist coverage.

MRCalderon3D/everything-game-dev-code · 19 tokens

patent-disclosure-reviewer

A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.

illusionaireal/oh-my-patent · 17 tokens

patent-mapper

Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.

revfactory/harness-100 · 37 tokens

security-engineer

Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).

ilyasibrahim/claude-agents-coordination · 41 tokens

osint-legal

Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.

reggiechan74/JobOps · 33 tokens

swiss-judicial-analyst

Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.

fedec65/bettercallclaude · 32 tokens