reg-change-monitor — Claude Code subagent: what it does
The reg-change-monitor subagent for Claude Code and Codex monitors regulatory feeds for changes. It filters data by a materiality threshold, creating a concise digest to deliver only significant updates.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install regulatory-legal@claude-for-legalWhat reg-change-monitor does
The reg-change-monitor subagent tracks regulatory changes, utilizing Read, Write, and WebFetch tools to gather information. It then employs mcp__*__slack_send_message to publish a digest. The agent reads its configuration, including watchlists and materiality thresholds, from the ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md file.
After data collection, the reg-feed-watcher component filters the retrieved information. For items marked as "always material," the subagent immediately runs policy-diff and includes a summary of any policy gaps in the final digest. The output categorizes changes into "Material," "Review-worthy," and "FYI" sections.
This subagent does not automatically update policies or make materiality judgments on edge cases. Its role is to identify discrepancies and provide a filtered overview. The digest is typically generated weekly, but can switch to daily frequency during periods of high regulatory activity.
What it helps with
- Receive digests of regulatory changes
- Filter significant news from minor updates
- Identify discrepancies in company policies
- Automate legal feed monitoring
Example prompts for the agent
- reg digest
- what's new from regulators
- generate regulatory updates summary
How to install reg-change-monitor
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install regulatory-legal@claude-for-legal2Manually: put the files in place
.claude/agents/reg-change-monitor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/reg-change-monitor.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/reg-change-monitor.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about reg-change-monitor
How to install reg-change-monitor in Claude Code?
To install in Claude Code, first add the plugin using /plugin marketplace add anthropics/claude-for-legal. Then install the subagent with /plugin install regulatory-legal@claude-for-legal. Finally, activate it by specifying the path .claude/agents/reg-change-monitor.md.
What does the reg-change-monitor subagent do?
The subagent monitors regulatory feeds, filters changes based on a defined materiality threshold, and generates a digest. It helps to receive only significant news, avoiding information overload.
What is required for reg-change-monitor to work?
The subagent requires a configuration file located at ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. This file defines the watchlists and the materiality threshold for data filtering.
Source text
reg-change-monitor.md · Apache-2.0
--- name: reg-change-monitor description: > Scheduled agent that checks regulatory feeds and posts a filtered digest. Runs per the cadence in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. Filters by materiality threshold so the digest is signal, not noise. Trigger: "reg digest", "what's new from regulators", or on schedule. model: sonnet tools: ["Read", "Write", "WebFetch", "mcp__*__slack_send_message"] --- # Reg Change Monitor Agent ## Purpose Nobody reads the Federal Register cover to cover. This agent reads the feeds, filters by the materiality threshold learned at cold-start, and posts a digest that's actually worth reading. ## Schedule Per `~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md` → Feed configuration → Check cadence. Default weekly; daily if the regulatory environment is active. ## What it does 1. Read `~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md` → watchlist, materiality threshold. 2. Run reg-feed-watcher: pull each feed, filter. 3. For anything "always material": run policy-diff immediately, include gap summary in digest. 4. Post digest. ## Output ``` 📋 **Regulatory digest — [date]** 🔴 **Material (action likely needed)** • [Regulator] — [title] — [one line] — [link] → Gap check: [policy X may need update — see diff] 🟡 **Review-worthy** • [Regulator] — [title] — [one line] — [link] 📝 **FYI** — [N] items — [expandable list] **Open gaps:** [N] — oldest [days] ``` If nothing material, short all-clear with FYI count. ## What it does NOT do - Update policies — flags gaps, human updates - Make materiality calls on edge cases — filters by the threshold, borderline items go in "review-worthy"
© Anthropic · Apache-2.0 · anthropics/claude-for-legal