achieving-cmmc-level-2-compliance

achieving-cmmc-level-2-compliance is a skill for Claude Code, Codex from Youngmaidainon/Agent-Level-Up. It costs 255 tokens per session (2,302 once invoked), scanned A, a copy of achieving-cmmc-level-2-compliance, MIT.

A procedure for preparing a defense contractor for Cybersecurity Maturity Model Certification (CMMC) Level 2, a U.S. Department of Defense security certification for protecting controlled information.

In plain words
What is it for?
It is for scoping systems that handle Controlled Unclassified Information, writing security plans and remediation plans, improving the SPRS score, and preparing for a C3PAO assessment.
Why use it?
It organizes the work needed to define the protected environment, meet 110 NIST security requirements, calculate the assessment score, and prepare evidence for an independent review.

Skill for Claude CodeCodex

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

Good fit It is for scoping systems that handle Controlled Unclassified Information, writing security plans and remediation plans, improving the SPRS score, and preparing for a C3PAO assessment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-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.

Any agent
npx skills add Youngmaidainon/Agent-Level-Up --skill achieving-cmmc-level-2-compliance
Clone the repo
git clone --depth 1 https://github.com/Youngmaidainon/Agent-Level-Up

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 achieving-cmmc-level-2-compliance

README.md
[![agentmods](https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-compliance/github.svg)](https://agentmods.dev/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-compliance)
Your own site
<a href="https://agentmods.dev/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-compliance"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-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 achieving-cmmc-level-2-compliance

Your own site · 80×15
<a href="https://agentmods.dev/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-compliance"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/achieving-cmmc-level-2-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 255 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,302 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 100% copy Near-identical to another mod 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.00255 $0.02302
Opus 5 $0.00128 $0.01151
Sonnet 5 $0.00051 $0.00460
Haiku 4.5 $0.00026 $0.00230

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

Security

Grade A, and why

achieving-cmmc-level-2-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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/process.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

100% identical to achieving-cmmc-level-2-compliance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cyber-security/ctf/achieving-cmmc-level-2-compliance/SKILL.md · 143 lines

How it starts

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

Achieving CMMC Level 2 Compliance

When to Use

  • When an organization in the Defense Industrial Base (DIB) stores, processes, or transmits Controlled Unclassified Information (CUI) under a DoD contract.
  • When a contract includes DFARS 252.204-7012 (safeguarding/incident reporting), -7019/-7020 (NIST 800-171 self-assessment + SPRS), or the new -7021 (CMMC requirement).
  • When preparing for a C3PAO third-party assessment or a DoD-led assessment.
  • When you must compute, post, or improve an SPRS score based on the NIST SP 800-171 DoD Assessment Methodology.
  • When authoring or remediating a System Security Plan (SSP) and POA&M for the 110 requirements.
  • When scoping which assets fall inside the CUI/FCI boundary (CUI assets, security-protection assets, contractor risk-managed assets, out-of-scope).

Prerequisites

  • Knowledge of which contracts carry CUI and the CUI categories involved (check the contract and the DoD CUI Registry).
  • An asset inventory and network diagram so you can define the CMMC assessment scope before assessing controls.
  • The NIST SP 800-171 Rev 2 requirements and the DoD Assessment Methodology scoring weights.
  • A documented SSP (its absence is itself a failed requirement — 3.12.4).
  • Identification of any External Service Providers (ESPs) / cloud services touching CUI, and whether they meet FedRAMP Moderate (or equivalency).

Workflow

1. Determine applicability and CUI categories

Confirm the contract requires CMMC Level 2 (CUI present, not just FCI). FCI-only contracts are Level 1 (the 15 FAR 52.204-21 requirements). Identify CUI categories from the contract and the DoD CUI Registry.

2. Scope the environment

Classify every asset into one of the CMMC scoping categories:

  • CUI Assets — process/store/transmit CUI (in scope, assessed against all applicable controls).
  • Security Protection Assets — provide security to the CUI environment (in scope).
  • Contractor Risk Managed Assets — could but are not intended to handle CUI; managed by policy.
  • Specialized Assets (IoT/OT, GFE, test equipment) — documented, limited assessment.
  • Out-of-Scope — physically/logically isolated from CUI.

Read the full file on GitHub · 143 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.

  1. 11d ago First seen · 143 lines · 255 tokens per session scan A f5124addbf04

Subscribe to this mod's changes

achieving-cmmc-level-2-compliance is a skill published in the GitHub repository Youngmaidainon/Agent-Level-Up (3 stars, last pushed 16d ago), licensed MIT. It adds 255 tokens to every session and 2,302 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to achieving-cmmc-level-2-compliance, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

achieving-cmmc-level-2-compliance

Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…

mukul975/Anthropic-Cybersecurity-Skills · 255 tokens

achieving-cmmc-level-2-compliance

Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…

adriannoes/awesome-agentic-ai · 255 tokens

achieving-cmmc-level-2-compliance

Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…

leecyno1/boutique-skills · 255 tokens

implementing-gdpr-data-protection-controls

The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill cover.

xalgorix/xalgorix · 52 tokens

implementing-pci-dss-compliance-controls

PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements.

xalgorix/xalgorix · 59 tokens

compliance

Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…

ericrisco/rsc-harness · 96 tokens