agentmods.dev

compliance-analysis

compliance-analysis is a command for coding agents from ololand-ai/ololand-plugins. It costs 33 tokens per session (480 once invoked), scanned A, original, Apache-2.0.

A deal-specific compliance check covering sanctions, antitrust filing thresholds, and national-security review. OFAC administers U.S. sanctions, HSR is the U.S. pre-merger notification process, and CFIUS reviews certain foreign investments in the United States.

In plain words
What is it for?
Screening entities against sanctions lists, reviewing HSR thresholds, and assessing CFIUS risk for a deal.
Why use it?
It brings several regulatory checks into one review and reports possible matches, filing requirements, exemptions, timing risks, and security concerns. The analysis can ask for missing deal details when they affect the result.

Command

Part of the ololand-dd plugin — 22 skills, 52 commands, 3 agents shipped together

not rated 0 yesterday A scan 33 tokens original Apache-2.0
View the source file ololand-ai/ololand-plugins
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.

agentmods
npx agentmods add commands/ololand-ai/ololand-plugins/compliance-analysis
Clone the repo
git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 52 commands, 3 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/compliance-analysis.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/compliance-analysis)
Your own site
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/compliance-analysis"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/compliance-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00033 $0.00480
Opus 5 $0.00016 $0.00240
Sonnet 5 $0.00007 $0.00096
Haiku 4.5 $0.00003 $0.00048

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

Security

Grade A, and why

compliance-analysis 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 5d 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/ololand-dd/commands/compliance-analysis.md · 46 lines

What it actually says

Compliance Analysis

Run OloLand's compliance workbench for sanctions, antitrust threshold, and national-security risk checks.

Usage

/compliance-analysis <deal_id> [ofac|hsr|cfius|all]

Arguments

  • deal_id (required) - The deal to analyze.
  • scope (optional) - ofac, hsr, cfius, or all. Default: all.

Execution

  1. For ofac or all, call run_ofac_screen(deal_id). Pass explicit entities or sdn_entries only if the user supplied them.
  2. For hsr or all, call run_hsr_analysis(deal_id). If the user supplies transaction value, buyer size, target size, or exemptions, pass those inputs through. Dollar inputs are in millions.
  3. For cfius or all, call run_cfius_risk(deal_id, ...). Ask for missing acquirer country, target industry, government ownership, critical technology, critical infrastructure, sensitive data, and government-contract flags when they materially affect the result.
  4. Use returned view_url values for web app handoff.

Output

Render:

  • OFAC - match status, matched entities, confidence, required remediation.
  • HSR - reportability status, thresholds crossed, exemptions, timing risk.
  • CFIUS - risk tier, drivers, mitigation path, filing recommendation.
  • Open diligence asks - missing identities, jurisdictions, NAICS/product categories, ownership, sensitive-data facts.

Guardrails

  • This is workflow support, not legal advice. Tell the user to involve counsel for filings, sanctions escalations, or CFIUS mitigation.
  • Do not treat missing acquirer/target details as clean results. Classify missing data as a gap.

Output URL Conventions

Use the tool-returned view_url. Canonical surface:

  • Compliance workbench: https://app.ololand.ai/deals/{deal_id}/analysis/compliance
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. 5d ago First seen · 46 lines · 33 tokens per session scan A d04c691c429f

Subscribe to this mod's changes

compliance-analysis is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 480 once invoked, about $0.0002 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.

Legal and compliance
Related

Other commands, from other repositories

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

review-epo-claims

Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.

RobThePCGuy/Claude-Patent-Creator · 22 tokens

voice-compliance

Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.

avelikiy/great_cto · 53 tokens

review-policy

Review a policy document for structure, coverage, and language quality.

mlunato47/claude-grc-plugin · 12 tokens

at-dsgvo

You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…

tractorjuice/arc-kit · 35 tokens

au-pspf

You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.

tractorjuice/arc-kit · 33 tokens