gap-analysis

gap-analysis is a command for coding agents from mlunato47/claude-grc-plugin. It costs 9 tokens per session (743 once invoked), scanned A, original, MIT.

A structured review that compares an organization's systems or services with a compliance framework, such as SOC 2, ISO 27001, or HIPAA.

In plain words
What is it for?
Use it to assess a defined scope—such as a cloud service, payment system, or patient portal—against frameworks including FedRAMP, SOC 2, ISO 27001, PCI, CMMC, or HIPAA.
Why use it?
It shows which required controls are implemented, partly implemented, planned, or missing, so readiness work has a clear structure.

Command

Part of the grc plugin — 1 skill, 24 commands, 1 agent shipped together

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/mlunato47/claude-grc-plugin/gap-analysis
Clone the repo
git clone --depth 1 https://github.com/mlunato47/claude-grc-plugin

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

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/gap-analysis.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/gap-analysis)
Your own site
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/gap-analysis"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/gap-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 743 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 $0.00009 $0.00743
Opus 5 $0.00005 $0.00371
Sonnet 5 $0.00002 $0.00149
Haiku 4.5 $0.00001 $0.00074

Measured 4d ago against content hash c4040206ccac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gap-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 4d 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:

grc/commands/gap-analysis.md · 108 lines

How it starts

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

/grc:gap-analysis

Perform a structured gap analysis against a compliance framework.

Usage

/grc:gap-analysis [framework] [scope-description]

Arguments

  • framework: The target compliance framework. Accepts same aliases as control-lookup.
  • scope-description: Brief description of what's in scope (system, organization, service).

Examples

/grc:gap-analysis fedramp moderate SaaS platform
/grc:gap-analysis soc2 security+availability cloud service
/grc:gap-analysis iso27001 entire organization
/grc:gap-analysis pci e-commerce payment processing
/grc:gap-analysis cmmc level2 CUI handling system
/grc:gap-analysis hipaa patient portal

Behavior

When invoked:

  1. Identify the framework and scope from arguments.

  2. Read the framework reference file and the readiness/gap analysis reference (audits/readiness-gap-analysis.md).

  3. Present a structured gap analysis template organized by:

    a. Control families/categories for the target framework b. Assessment criteria per control area:

    • Implemented (control fully in place with evidence)
    • Partially Implemented (some aspects in place)
    • Planned (not yet implemented but on roadmap)
    • Not Implemented (no plans currently)
    • Not Applicable (with justification) c. Maturity assessment (optional):
    • Level 0: Non-existent
    • Level 1: Ad-hoc
    • Level 2: Repeatable
    • Level 3: Defined
    • Level 4: Managed
    • Level 5: Optimizing
  4. For each control family, provide:

    • Key controls to assess
    • Questions to ask during assessment
    • Evidence to look for
    • Common gaps in that area
    • Remediation complexity estimate (Low/Medium/High)
  5. Generate a gap analysis worksheet the user can work through interactively:

    • Walk through each control family
    • Ask about current state
    • Record gaps
    • Build prioritized remediation roadmap
  6. If the user provides current-state information, assess gaps and produce:

    • Gap summary heat map (by family)
    • Prioritized findings
    • Remediation roadmap with effort estimates
    • Quick wins vs long-term items

Read the full file on GitHub · 108 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. 4d ago First seen · 108 lines · 9 tokens per session scan A c4040206ccac

Subscribe to this mod's changes

gap-analysis is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 743 once invoked, about $0.0000 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.