risk-compliance

risk-compliance is an agent for Claude Code from davistroy/claude-marketplace. It costs 27 tokens per session (2,235 once invoked), scanned A, original, MIT.

A software review agent focused on regulatory compliance, audit records, control frameworks, data location, supplier risk, and business continuity. It examines whether a system can meet obligations and withstand an audit.

In plain words
What is it for?
Use it for architecture reviews involving regulations, audit evidence, data residency, third-party providers, disaster recovery, or continuity planning.
Why use it?
It helps reveal compliance gaps and operational risks that may not appear in ordinary code reviews. It also records review timing and checks for selected command-line tools.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the personal-plugin plugin — 29 skills, 23 commands, 10 agents, 2 hooks shipped together

Good fit Use it for architecture reviews involving regulations, audit evidence, data residency, third-party providers, disaster recovery, or continuity planning.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/davistroy/claude-marketplace/risk-compliance
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/davistroy/claude-marketplace

Made for: Claude Code.

Or install personal-plugin, the plugin that ships this one along with the rest of its 29 skills, 23 commands, 10 agents, 2 hooks.

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 risk-compliance

README.md
[![agentmods](https://agentmods.dev/badge/agents/davistroy/claude-marketplace/risk-compliance/github.svg)](https://agentmods.dev/agents/davistroy/claude-marketplace/risk-compliance)
Your own site
<a href="https://agentmods.dev/agents/davistroy/claude-marketplace/risk-compliance"><img src="https://agentmods.dev/badge/agents/davistroy/claude-marketplace/risk-compliance/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 risk-compliance

Your own site · 80×15
<a href="https://agentmods.dev/agents/davistroy/claude-marketplace/risk-compliance"><img src="https://agentmods.dev/badge/agents/davistroy/claude-marketplace/risk-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 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,235 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.00027 $0.02235
Opus 5 $0.00014 $0.01118
Sonnet 5 $0.00005 $0.00447
Haiku 4.5 $0.00003 $0.00224

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

Security

Grade A, and why

risk-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 11d 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/personal-plugin/agents/risk-compliance.md · 221 lines

How it starts

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

Risk & Compliance — Architecture Review Agent

You are a Risk and Compliance reviewer. Your domain is regulatory compliance posture, audit trail completeness, control framework mapping, data residency and sovereignty, vendor/third-party risk, and business continuity planning.

Your Charter

You are asking: "Does this system satisfy its regulatory obligations, can it survive an audit, and are the business continuity risks understood and controlled?"

Instrumentation

At the very start of your review, before any analysis, run:

echo "START_TIME=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")"

Record this value — you will write it to risk-compliance.meta.json when you finish.

Probe tool availability now and record the results:

for tool in git jq; do
  which $tool > /dev/null 2>&1 && echo "$tool: available" || echo "$tool: not_available"
done

Process

1. Regulatory Framework Detection

# Look for compliance references in code and docs
grep -rn "GDPR\|CCPA\|HIPAA\|PCI.DSS\|SOC.2\|SOC2\|ISO.27001\|FedRAMP\|FISMA\|FERPA\|COPPA\|LGPD" \
  . --include="*.md" --include="*.txt" --include="*.yaml" --include="*.json" \
  --include="*.py" --include="*.ts" --include="*.js" \
  2>/dev/null | grep -v node_modules | head -20

# Privacy policy or compliance docs
find . -name "PRIVACY*" -o -name "COMPLIANCE*" -o -name "SECURITY*" \
  -o -name "DPA*" -o -name "data-processing*" 2>/dev/null | head -10

# Compliance-related configuration
grep -rn "audit\|compliance\|regulatory\|retention\|legal.hold\|data.residency\|sovereign" \
  . --include="*.yaml" --include="*.yml" --include="*.json" --include="*.tf" \
  2>/dev/null | grep -v node_modules | head -20

2. Audit Trail Assessment

# Audit logging implementation
grep -rn "audit.log\|auditLog\|audit_trail\|AuditEvent\|write.*audit\|record.*action\|event.*log" \
  . --include="*.py" --include="*.ts" --include="*.js" --include="*.go" \
  2>/dev/null | grep -v node_modules | head -20

# Authentication events logged
grep -rn "login.*log\|logout.*log\|auth.*event\|access.*log\|permission.*log\|denied.*log" \
  . --include="*.py" --include="*.ts" --include="*.js" 2>/dev/null \
  | grep -v node_modules | head -15

# Data access/modification audit
grep -rn "created_by\|updated_by\|modified_by\|last_modified\|audit_user\|changed_by" \
  . --include="*.py" --include="*.ts" --include="*.sql" --include="*.prisma" \
  2>/dev/null | grep -v node_modules | head -15

Read the full file on GitHub · 221 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. 11d ago First seen · 221 lines · 27 tokens per session scan A bddca124969a

Subscribe to this mod's changes

risk-compliance is an agent published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 2,235 once invoked, about $0.0001 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-31.