A command for checking a Customer Responsibility Matrix or Customer Implementation Summary against security requirements. These documents describe which security responsibilities belong to the customer and which belong to a provider.

Use it to review a responsibility document against a security framework and impact level such as FedRAMP Moderate or High.

It identifies missing coverage, unclear statements, and incomplete security documentation for selected FedRAMP, NIST, or FISMA baselines.

review-crm — Command for Claude Code by mlunato47

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/mlunato47/claude-grc-plugin

Made for: Claude Code.

Or install grc, the plugin that ships this one along with the rest of its 1 skill, 24 commands.

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/commands/mlunato47/claude-grc-plugin/review-crm/github.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/review-crm)

Your own site

<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/review-crm"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/review-crm/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/commands/mlunato47/claude-grc-plugin/review-crm"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/review-crm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,456 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.00010	$0.01456
Opus 5	$0.00005	$0.00728
Sonnet 5	$0.00002	$0.00291
Haiku 4.5	$0.00001	$0.00146

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

Security

Grade A, and why

review-crm 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

review-crm — 100% identical, 0 lines differ

grc/commands/review-crm.md · 152 lines

How it starts

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

/grc:review-crm

Review a Customer Responsibility Matrix (CRM) or Customer Implementation Summary (CIS) for coverage, clarity, and completeness.

Usage

/grc:review-crm [framework?] [baseline?]

The user pastes their CRM content after invoking the command.

Arguments

framework (optional): fedramp, nist, fisma. Defaults to fedramp.
baseline (optional): low, moderate, high. Defaults to moderate.

Examples

/grc:review-crm
/grc:review-crm fedramp moderate
/grc:review-crm fedramp high
/grc:review-crm nist moderate

Behavior

When invoked:

Display the Data Sensitivity Notice at the top of every response (see SKILL.md Data Handling section).
Read the appropriate reference files:
- skills/grc-knowledge/audits/document-section-requirements.md for CRM requirements and expected distribution
- Framework file from skills/grc-knowledge/frameworks/ for baseline control list
- skills/grc-knowledge/audits/narrative-quality-criteria.md for quality indicators
Evaluate the CRM against these criteria:

a. Coverage Assessment
- Count controls/families present in the CRM vs. total baseline controls
- Calculate overall coverage percentage
- Identify missing control families entirely
- Identify individual controls with customer responsibility that are not addressed
b. Responsibility Distribution Categorize each control's designation and report the distribution:
- CSP-Implemented: CSP fully handles
- Customer-Implemented: Customer must fully implement
- Shared: Both parties (must specify the split)
- Inherited: From underlying infrastructure provider Compare the distribution against expected patterns (see document-section-requirements.md)
c. Clarity Assessment For each entry (especially Shared controls):
- Is the customer's responsibility clearly described?
- Are specific actions identified (not just "customer is responsible")?
- Are customer-responsible ODP values called out?
- Can a customer read this and know exactly what they need to do?

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

9d ago First seen · 152 lines · 10 tokens per session scan A 2ed40b9bcf1e

Subscribe to this mod's changes

review-crm is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,456 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-30.

Documents Security

brand-generate

Generate an on-brand document from a saved Brand Profile.

ferdinandobons/brand-docs · 0 tokens

cti-report

Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].

7onez/cti-expert · 45 tokens

prose-review-docs

Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…

ihudak/ihudak-claude-plugins · 67 tokens

review-crm