soc2-ccm-continuous-monitoring

soc2-ccm-continuous-monitoring is a skill for Claude Code, Codex from vaquarkhan/compliance-agent-skills. It costs 111 tokens per session (1,806 once invoked), scanned A, original, MIT.

A continuous control monitoring approach for SOC 2, an audit framework for service security and trust controls. It describes scheduled control tests, configuration-drift checks, risk scoring, and alerts for agent platforms, MCP servers, and cloud infrastructure.

In plain words
What is it for?
Use it to monitor IAM, firewalls, MCP tool allowlists, agent skills, and other configurations; track control health; alert on regressions; and connect compliance checks with CI/CD tools such as Terraform or OPA.
Why use it?
It helps organizations detect when systems or security controls change between audits instead of relying only on occasional point-in-time checks. It can also highlight repeated failures and overdue fixes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to monitor IAM, firewalls, MCP tool allowlists, agent skills, and other configurations; track control health; alert on regressions; and connect compliance checks with CI/CD tools such as Terraform or OPA.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring
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 vaquarkhan/compliance-agent-skills --skill soc2-ccm-continuous-monitoring
Clone the repo
git clone --depth 1 https://github.com/vaquarkhan/compliance-agent-skills

Made for: Claude Code, Codex.

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 soc2-ccm-continuous-monitoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring/github.svg)](https://agentmods.dev/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring)
Your own site
<a href="https://agentmods.dev/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring/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 soc2-ccm-continuous-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring"><img src="https://agentmods.dev/badge/skills/vaquarkhan/compliance-agent-skills/soc2-ccm-continuous-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,806 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.00111 $0.01806
Opus 5 $0.00056 $0.00903
Sonnet 5 $0.00022 $0.00361
Haiku 4.5 $0.00011 $0.00181

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

Security

Grade A, and why

soc2-ccm-continuous-monitoring 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 12d 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.

skills/soc2-ccm-continuous-monitoring/SKILL.md · 157 lines

How it starts

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

SOC 2 CCM Continuous Monitoring

Overview

Continuous Control Monitoring (CCM) satisfies SOC 2 CC4.1 (monitoring activities) and CC7.x (system monitoring) by automating control tests on a schedule and alerting on drift. This skill operationalizes monitoring between annual audits—replacing point-in-time compliance with always-on assurance.

Components:

  1. Control test automation: scheduled scripts/MCP jobs per TSC control
  2. Drift detection: baseline vs current config comparison
  3. Predictive risk scores: weighted FAIL trends, mean-time-to-remediate
  4. Alert routing: Slack MCP, SIEM, ticketing integration

When to Use

Use this skill when:

  • Implementing always-on SOC 2 monitoring (Vanta/Drata-style continuous controls)
  • Detecting configuration drift (IAM, firewall, MCP tool allowlists, agent skills)
  • Building executive risk dashboards with control health scores
  • Transitioning from Type I point-in-time to Type II period-of-time readiness
  • Alerting on regression after remediation (control was PASS, now FAIL)
  • Integrating compliance scans into CI/CD (Terraform, OPA policy checks)

Do not use this skill when:

  • One-time audit evidence packaging (use soc2-evidence-collection)
  • Initial control design gap analysis (use soc2-trust-services-criteria)
  • PCI weekly script tamper detection (use pci-dss-script-audit 11.6.1 workflow)

Core Process

Execute steps in order.

Step 1: Control inventory for monitoring

  1. Import TSC control matrix from soc2-trust-services-criteria output.
  2. Filter controls suitable for automated testing (target ≥70% automation for CC6/CC7):
    • MFA enforcement, password policy, encryption at rest flags
    • Public S3 bucket detection, security group overly permissive rules
    • MCP OAuth scope drift, agent skill directory checksum changes
    • Failed login rate thresholds, backup success signals
  3. Mark each control: AUTOMATED, SEMI-AUTO, MANUAL.
  4. Artifact: ccm-control-inventory-{id}.json.

Read the full file on GitHub · 157 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. 12d ago First seen · 157 lines · 111 tokens per session scan A 1f392ccd5b3d

Subscribe to this mod's changes

soc2-ccm-continuous-monitoring is a skill published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 18d ago), licensed MIT. It adds 111 tokens to every session and 1,806 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

cmmc-assessment-objectives

Verbatim reference for all 320 NIST 800-171A Rev 2 assessment objectives, plus the Rev 2 → Rev 3 control crosswalk. Use for AO-level lookups (e.g., 3.1.1[c]), evidence planning, and forward-mapping to Rev 3. Pairs with cmmc-expert.

GRCEngClub/claude-grc-engineering · 80 tokens

dora-expert

DORA expert for EU financial entities. Deep knowledge of Digital Operational Resilience Act including 5 pillars, ICT risk management, incident reporting, resilience testing, third-party oversight, and information sharing for financial sector digital resilience.

GRCEngClub/claude-grc-engineering · 49 tokens

cmmc-expert

CMMC v2.0 expert for DoD contractors. Covers NIST 800-171 Rev 2 (14 families, 110 controls), SPRS scoring, POA&M rules, 32 CFR Part 170, DFARS clauses, scoping, ESP/CSP, C3PAO assessment lifecycle, and Rev 2 → Rev 3 transition.

GRCEngClub/claude-grc-engineering · 80 tokens

eu-nis2-expert

EU NIS2 Directive (Directive (EU) 2022/2555) expert. Reference-depth knowledge of essential vs important entity classification, Article 20 governance, the Article 21 ten cybersecurity risk-management measures, the Article 23 24h/72h/1mo incident-reporting timeline, and supervision/enforcement under Articles 32-34.…

GRCEngClub/claude-grc-engineering · 90 tokens

gdpr-expert

GDPR expert for EU privacy compliance. Deep knowledge of General Data Protection Regulation including 99 articles, 7 principles, 6 lawful bases, data subject rights, DPO requirements, DPIA, breach notification, cross-border transfers, and enforcement.

GRCEngClub/claude-grc-engineering · 55 tokens

glba-expert

GLBA expert for financial institutions. Deep knowledge of Gramm-Leach-Bliley Act including Safeguards Rule (16 CFR Part 314), Privacy Rule (16 CFR Part 313), FTC enforcement, information security program requirements, vendor management, and consumer privacy notices.

GRCEngClub/claude-grc-engineering · 58 tokens