A collection of tools for managing regulatory compliance, meaning the work of meeting laws, standards, and customer security requirements.

Use it to manage governance, risk, and compliance work across regulations such as SOC 2, GDPR, ISO 27001, HIPAA, PCI DSS, and FedRAMP.

It organizes compliance work from defining what applies through fixing gaps, collecting proof, certification, and ongoing monitoring.

compliance — Plugin by bromso

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.

Claude Code

/plugin marketplace add bromso/metapowers

agentmods

npx agentmods add plugins/bromso/metapowers/compliance

Clone the repo

git clone --depth 1 https://github.com/bromso/metapowers

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

compliance 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 2d 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/compliance/.claude-plugin/plugin.json · 26 lines

What it actually says

{
	"name": "compliance",
	"version": "0.1.0",
	"description": "GRC Compliance Lifecycle — scope, assess, remediate, certify, monitor with 48 skills across 30+ regulations",
	"author": { "name": "Jonas Broms" },
	"repository": "https://github.com/bromso/metapowers",
	"homepage": "https://bromso.github.io/metapowers/",
	"license": "MIT",
	"keywords": [
		"compliance",
		"grc",
		"soc2",
		"gdpr",
		"iso27001",
		"hipaa",
		"pci-dss",
		"fedramp",
		"audit"
	],
	"skills": "../skills/",
	"commands": "../commands/",
	"agents": "../agents/",
	"hooks": "../hooks/hooks.json",
	"mcpServers": "../.mcp.json"
}

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.

2d ago First seen · 26 lines scan A ef198968e0d4

Subscribe to this mod's changes

compliance is a plugin published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Planning Security claude-agent claude-code claude-code-plugin claude-skills context-design context-engineering

compliance

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

memodb-io

claude-plugin

titen

axme-code

wordcount-habitat

cortadel