regulatory-updates

regulatory-updates is a skill for Claude Code from bromso/metapowers. It costs 73 tokens per session (1,072 once invoked), scanned A, original, MIT.

A regulatory change implementation plan explains how a new or amended law affects an organisation. It assigns owners, resources, review items, and dated steps for becoming ready before the law takes effect.

In plain words
What is it for?
It helps assess the impact of a specific law, rate its urgency, create an implementation timeline, assign responsibility, and prepare issues for legal review.
Why use it?
It turns a legal change into trackable work rather than leaving teams to interpret the deadline and impact separately. It also identifies questions that need advice from counsel.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the legal plugin — 35 skills shipped together

Good fit It helps assess the impact of a specific law, rate its urgency, create an implementation timeline, assign responsibility, and prepare issues for legal review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bromso/metapowers/regulatory-updates
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.

Any agent
npx skills add bromso/metapowers --skill regulatory-updates
Clone the repo
git clone --depth 1 https://github.com/bromso/metapowers

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 35 skills.

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 regulatory-updates

README.md
[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/regulatory-updates/github.svg)](https://agentmods.dev/skills/bromso/metapowers/regulatory-updates)
Your own site
<a href="https://agentmods.dev/skills/bromso/metapowers/regulatory-updates"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/regulatory-updates/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 regulatory-updates

Your own site · 80×15
<a href="https://agentmods.dev/skills/bromso/metapowers/regulatory-updates"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/regulatory-updates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,072 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.00073 $0.01072
Opus 5.5 $0.00029 $0.00429
Sonnet 5.5 $0.00015 $0.00214
Haiku 4.5 $0.00007 $0.00107

Measured 3d ago against content hash 50b90fdb2593, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

regulatory-updates 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 3d 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.

plugins/legal/skills/regulatory-updates/SKILL.md · 87 lines

How it starts

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

Regulatory Updates

Track and assess the impact of new or changing regulations for "$ARGUMENTS". Research recent regulatory changes, assess their impact on current compliance posture, and create implementation timelines.

Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/legal/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.

Prerequisites

Check that .metapowers/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:

"Run an Assess skill first (e.g. /legal:risk-assessment <project>) to generate the prerequisite assessment artifact."

Process

  1. Read inputs:

    • Read .metapowers/legal/<project>/00-assess.md for current regulatory landscape, jurisdiction, and compliance status
    • Review any existing compliance artifacts in .metapowers/legal/<project>/
  2. Research regulatory changes:

    • Use WebSearch to find recent and upcoming regulatory changes relevant to ""
    • Focus on the jurisdictions and regulation types identified in the assessment
    • Search for proposed legislation, final rules, guidance updates, and enforcement trends
    • Check regulatory body announcements, industry association updates, and legal news sources
  3. Summarize each regulatory change:

    • What is changing — clear description of the new requirement or modification
    • Effective date — when the change takes effect or compliance is required
    • Who it affects — which teams, processes, or systems are impacted
    • What action is needed — specific steps required to comply

Read the full file on GitHub · 87 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. 3d ago First seen · 87 lines · 73 tokens per session scan A 50b90fdb2593

Subscribe to this mod's changes

regulatory-updates is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,072 once invoked, about $0.0003 per session on Opus 5.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-10-21.

Related

Other skills, from other repositories

chief-human-resources-officer

Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…

cbrock84/headcount · 0 tokens

tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…

cbrock84/headcount · 75 tokens

contract-review

Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback…

cbrock84/headcount · 74 tokens

corporate-governance

Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval…

cbrock84/headcount · 88 tokens

performance-management

Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.

cbrock84/headcount · 59 tokens

design-method

Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.

fusengine/agents · 35 tokens