dataroom-watcher

dataroom-watcher is an agent for Claude Code from anthropics/claude-for-legal. It costs 53 tokens per session (549 once invoked), scanned A, original, Apache-2.0.

A scheduled helper that checks a virtual data room, an online repository for deal documents, for new uploads and reports closing-checklist status.

In plain words
What is it for?
It is for monitoring uploads, matching documents to request categories, flagging material contracts, litigation, and intellectual-property files, and writing updates to Slack or a fallback file.
Why use it?
It helps deal teams notice late document changes and track important diligence or closing items before calls and deadlines.

Agent for Claude Code ✓ vendor

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

Part of the corporate-legal plugin — 10 skills, 1 agent shipped together

Good fit It is for monitoring uploads, matching documents to request categories, flagging material contracts, litigation, and intellectual-property files, and writing updates to Slack or a fallback file.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/anthropics/claude-for-legal/dataroom-watcher
About the project

Claude for Legal is a collection of AI agents, skills, and data connectors for legal work such as commercial, privacy, employment, litigation, regulatory, and intellectual-property matters. Lawyers and legal teams use it through Claude Cowork, Claude Code, or the Claude Managed Agents API, with attorney review required for every output. The catalogue entries are its workflow plugins, skills, agents, and connectors.

anthropics/claude-for-legal · 9,433 stars · on GitHub

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/anthropics/claude-for-legal

Made for: Claude Code.

Or install corporate-legal, the plugin that ships this one along with the rest of its 10 skills, 1 agent.

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 dataroom-watcher

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

agentmods 80×15 button for dataroom-watcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/anthropics/claude-for-legal/dataroom-watcher"><img src="https://agentmods.dev/badge/agents/anthropics/claude-for-legal/dataroom-watcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 549 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.00053 $0.00549
Opus 5 $0.00026 $0.00275
Sonnet 5 $0.00011 $0.00110
Haiku 4.5 $0.00005 $0.00055

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

Security

Grade A, and why

dataroom-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 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

Copies of this mod

1 near-identical copy found in the catalogue:

corporate-legal/agents/dataroom-watcher.md · 55 lines

What it actually says

Dataroom Watcher Agent

Purpose

VDRs get updated at 11pm the night before a call. This agent watches for new uploads and tells the team what came in. Also runs the closing checklist status on the configured cadence.

Schedule

Daily during active diligence. Checklist status per ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md → Deal team briefing cadence.

Integrations

Posting to Slack requires a Slack MCP server in your environment. This plugin does not bundle one. If no Slack MCP is configured, write the VDR update and checklist status to a file in ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/updates/[date].md and notify the user — do not fail silently.

VDR tools (Box, Intralinks, Datasite) are likewise external MCPs — if none are connected, prompt the user for the VDR export or ask them to update ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/vdr-inventory.md manually.

What it does

  1. Query VDR for documents added since last run.
  2. Map new docs to request list categories.
  3. Flag anything in high-priority categories (Material Contracts, Litigation, IP).
  4. Run closing-checklist Mode 4 if it's briefing day.
  5. Post to deal channel.

Output

📁 **VDR update — [deal code] — [date]**

**New since [last run]:** [N] docs

**Priority categories:**
• /02-Contracts/Customer/ — [N] new ([filenames])
• /05-Litigation/ — [N] new ⚠️

**Other:** [N] docs in [categories]

[If briefing day: closing checklist status per Mode 4]

What it does NOT do

  • Read the new docs — flags them for review, human reads
  • Update the closing checklist — reports status, human updates
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 · 55 lines · 53 tokens per session scan A 87407876b1aa

Subscribe to this mod's changes

dataroom-watcher is an agent published in the GitHub repository anthropics/claude-for-legal (9,433 stars, last pushed 21d ago), licensed Apache-2.0. It adds 53 tokens to every session and 549 once invoked, about $0.0003 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-30.