score-maturity

score-maturity is a command for Claude Code from mlunato47/claude-grc-plugin. It costs 12 tokens per session (1,700 once invoked), scanned A, original, MIT.

A command that rates how fully a security or compliance control is implemented, from 0 to 5, using a named framework such as NIST, FedRAMP, or SOC 2.

In plain words
What is it for?
Use it to assess a control, control family, or framework baseline and get guidance for reaching the next maturity level.
Why use it?
It turns a written description or answers to structured questions into a consistent maturity rating and shows what to improve next.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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/score-maturity
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, 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 score-maturity

README.md
[![agentmods](https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/score-maturity.svg)](https://agentmods.dev/commands/mlunato47/claude-grc-plugin/score-maturity)
Your own site
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/score-maturity"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/score-maturity.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 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,700 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.1 $0.00012 $0.01700
Opus 5 $0.00006 $0.00850
Sonnet 5 $0.00002 $0.00340
Haiku 4.5 $0.00001 $0.00170

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

Security

Grade A, and why

score-maturity 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 6d 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/score-maturity.md · 173 lines

How it starts

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

/grc:score-maturity

Score control implementation maturity on a 0–5 scale with actionable guidance to reach the next level.

Usage

/grc:score-maturity [framework] [family-or-control] [baseline?]

The user optionally provides implementation descriptions or narrative text. If no content is provided, the command asks structured questions.

Arguments

  • framework: The compliance framework. Accepts: nist, fedramp, fisma, cmmc, soc2, iso27001, pci, hipaa, cis, cobit
  • family-or-control: A control family (e.g., ac, ia) or specific control ID (e.g., ac-2, ia-2)
  • baseline (optional): low, moderate, high. Defaults to moderate for NIST/FedRAMP.

Examples

/grc:score-maturity fedramp ac-2
/grc:score-maturity fedramp ac moderate
/grc:score-maturity nist ia
/grc:score-maturity cmmc 3.5
/grc:score-maturity soc2 CC6
/grc:score-maturity cobit DSS02

Behavior

When invoked:

  1. Display the Data Sensitivity Notice at the top of every response if the user provides content. If no content is provided and the command enters interactive/question mode, the notice is not needed.

  2. Read the appropriate reference files:

    • skills/grc-knowledge/audits/narrative-quality-criteria.md for the 0–5 maturity scale
    • Framework file from skills/grc-knowledge/frameworks/ for control details
  3. Determine mode based on user input:

    Mode A: Content-based scoring (user provides narrative or implementation description)

    • Score each control directly using the 0–5 maturity scale
    • Apply the same criteria as /grc:review-narrative but focus on the score and "next level" guidance
    • For a family, score each control individually and compute an overall family score

    Mode B: Question-based scoring (no content provided)

    • Ask structured questions about the implementation for each control or the family
    • Questions organized around the Five W's and maturity indicators:

    For each control, ask about:

    1. Documentation: Is there a written narrative? How detailed?
    2. Implementation: Is the control technically implemented? Fully or partially?
    3. Automation: Is the control automated, manual, or hybrid?
    4. Repeatability: Is the process consistent and repeatable? Documented procedures?
    5. Measurement: Are there metrics? How is effectiveness tracked?
    6. Review: When was the last review? How often?
    7. Evidence: What evidence exists? Could you produce it for an auditor today?

Read the full file on GitHub · 173 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. 6d ago First seen · 173 lines · 12 tokens per session scan A 9fc7ec6e69a7

Subscribe to this mod's changes

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

Related

Other commands, from other repositories