What is oc-compliance-ops?

A compliance workflow that maps standards such as SOC 2, HIPAA, and GDPR to code, configuration, tests, policies, and audit records. It maintains a control register and collects evidence bundles for releases and deployments.

Use it to define compliance scope, track controls, generate audit evidence, and prepare policy documents.

It replaces a last-minute audit scramble with an up-to-date record of which controls apply and what evidence supports them.

oc-compliance-ops — Skill for Claude Code by asfbay-bit/opchain-skills

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 asfbay-bit/opchain-skills --skill oc-compliance-ops

Clone the repo

git clone --depth 1 https://github.com/asfbay-bit/opchain-skills

Made for: Claude Code.

Or install opchain, the plugin that ships this one along with the rest of its 36 skills, 16 commands, 3 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-compliance-ops/github.svg)](https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-compliance-ops)

Your own site

<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-compliance-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-compliance-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-compliance-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-compliance-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 208 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,765 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.

Model	Per session	Once invoked
Fable 5.1	$0.00208	$0.03765
Opus 5.5	$0.00083	$0.01506
Sonnet 5.5	$0.00042	$0.00753
Haiku 4.5	$0.00021	$0.00377

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

Security

Grade A, and why

oc-compliance-ops 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 26d 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/opchain/skills/oc-compliance-ops/SKILL.md · 303 lines

How it starts

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

Compliance Ops

On first invocation, read references/orchestrator.md and follow its welcome protocol.

Compliance Ops turns compliance from an annual scramble into a standing property of the pipeline. Three artifacts, all in-repo and reviewed like code:

The profile (.opchain/compliance.yaml) — which frameworks apply, to which data, at what tier.
The control register (the register: block of the same file) — every applicable control mapped to the concrete artifact that satisfies it (a config, a test, a policy doc, an audit-log query), with a status.
The evidence bundle — generated per deploy/release: the register's artifacts collected, stamped with SHA + date, ready to hand an auditor.

What this skill is not: it does not certify (formal audits need qualified auditors), it does not give legal advice, it does not assess posture (oc-security-auditor's /oc-security readiness is the point-in-time gap assessor — this skill consumes that output), and it does not execute technical fixes (oc-security-hardening does).

Command Reference

COMPLIANCE OPS COMMANDS

  /oc-comply               Show this menu
  /oc-comply scope         Declare frameworks, data classes, tier → write the profile
  /oc-comply register      Build or maintain the control register
  /oc-comply evidence      Generate the evidence bundle for a deploy/release
  /oc-comply gaps          Open controls: unmapped, unsatisfied, or stale
  /oc-comply policies      Scaffold/update policy docs the frameworks require
  /oc-comply status        Register health + last evidence bundle
  /oc-compliance           Alias for /oc-comply

  /checkpoint              Show oc-compliance-ops checkpoint

`/oc-comply scope`

Declare — do not assume — what applies:

Question	Drives
Which frameworks? (SOC 2, HIPAA, GDPR, none-yet)	Which control sets enter the register
Which data classes exist? (reuse oc-security-auditor's PUBLIC/INTERNAL/CONFIDENTIAL/RESTRICTED)	Which controls are applicable vs. N/A
What tier? (pre-revenue prep · active-audit · maintaining)	Register depth and evidence cadence

Read the full file on GitHub · 303 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

26d ago Changed d039a45c7187
29d ago Changed 3d811be4e517
1mo ago Changed 073c036cc3c4
1mo ago Changed · +21 lines 384dada202ea
1mo ago First seen · 282 lines · 208 tokens per session scan A 9f294c24b42f

Subscribe to this mod's changes

oc-compliance-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 208 tokens to every session and 3,765 once invoked, about $0.0008 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-09-04.

Legal and compliance Security

fto-triage

Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…

anthropics/claude-for-legal · 81 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

oc-compliance-ops